Command Center User Guide 4 1

8/10/2019 Command Center User Guide 4 1

1/220


2/220

Copyright and Trademark Notice

Use of the product documented in this guide is subject to your prior acceptance of the End User License Agreement.

Information in this document is subject to change without notice. Companies, names, and data used in examples herein

are fictitious unless otherwise noted. No part of this document may be reproduced or transmitted in any form or by any

means, electronic or mechanical, for any purpose, without the express written permission of Citrix Systems, Inc.

2003-2010 Citrix Systems, Inc. All rights reserved.

This product includes code licenced from RSA Data Security. RSA Encryption

RSA Security Inc., All Rights Reserved.

This product includes software developed by The Apache Software Foundation (http://www.apache.org/).

This product includes software developed by Adventnet, Inc. (http://www.adventnet.com) Adventnet, Inc. All rights

reserved.

Trademark Acknowledgements

Citrix NetScaler, Citrix Branch Repeater, Citrix Access Gateway, and Citrix Command Center are registered trademarks

of Citrix Systems, Inc. in the United States and other countries.

Java, Sun, and SunOS are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other

countries. Sun Microsystems, Inc has not tested or approved this product.

Portions of this software are based in part on the work of the Independent JPEG Group.

Microsoft, MS-DOS, Windows, Windows Media, Windows Server, Windows NT, Windows XP, Win32, Outlook, ActiveX,

Active Directory, and DirectShow are either registered trademarks or trademarks of Microsoft Corporation in the United

States and/or other countries.

Copyright 2001, Thai Open Source Software Center Ltd, Sun Microsystems. All Rights Reserved.

All other trademarks and registered trademarks are the property of their respective owners.

Release: 4.1

Document code: March 28 2011 04:46:05


3/220


4/220

Finding Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30

To find devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30To find devices based on specific criteria... .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..30

4 Monitoring and Managing Events Generated on Citrix Devices.. . .. . .. . .. .. . .. . .. .. . .. . .. .. . .. .31Monitoring SNMP Events and Alarms.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .32

Viewing Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32

Viewing Alarms.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32

Configuring Views for Events and Alarms .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .33

Managing SNMP Events and Alarms .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .33

Monitoring Syslog Events.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34

Configuring Command Center as the Syslog Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34To configure Command Center as the syslog server. . . . . . . . . . . . . . . . . . . . . . . . . . . . .34

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35

Viewing Syslog Messages.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35

Configuring Syslog Views... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35

Configuring Event and Alarm Triggers.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .35

5 Monitoring and Managing the Real-Time Status of Entities Configured on NetScaler

Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Monitoring Virtual Servers, Services, and Service Groups..................................38

Viewing the Status of Virtual Servers.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .38Viewing the Status of Services.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39

Viewing the Status of Service Groups.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..39

Configuring Views.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40

Managing the Real-Time Status of Entities..................................................40

Configuring the Polling Interval.........................................................41

Enabling or Disabling Virtual Servers...................................................41

Enabling or Disabling Services.........................................................41

Enabling or Disabling Service Groups.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..41

Viewing the Audit Trai l . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42

6 Using Tasks to Configure Managed Devices.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43Managing Built-in Tasks.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44

Upgrading NetScaler with Built-in Tasks.. .. .. .. .. .. . .. .. .. .. . .. .. .. .. .. .. .. .. . .. .. .. ..44

Configuring NetScaler with Built-in Tasks... .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .44

Upgrading Repeater with Built-in Tasks................................................45

Configuring Repeater with Built-in Tasks.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .45

Executing Built-in Tasks... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45

Contents

iv


5/220

Viewing the Execution Log for Specific Built-in Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46

Scheduling Built-in Tasks... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Exporting Built-in Tasks... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Configuring Custom Tasks... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Adding Custom Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47

Executing Custom Tasks... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48

Viewing the Execution Log for Specific Custom Tasks.. .. .. .. .. .. .. . .. .. .. .. .. .. .. .. ..49

Scheduling Custom Tasks... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Exporting Custom Tasks... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Customizing Built-in and Custom Tasks.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. . 50

Viewing the Execution Log for all Tasks.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. . 50

7 Monitoring and Managing SSL Certificates Configured on NetScaler Devices . . . . . . . . . . . . . . . .51Enabling or Disabling Certificate Management .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .52

Setting the Polling Interval for SSL Certificates ... .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..52

Setting the Expiry Criteria of SSL Certificates ... .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. . 52

Generating Certificate Signing Requests . .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 52

Updating SSL Certificates .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53

Viewing the Audit Trail for SSL Certificates .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .53

Downloading SSL Certificates .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53

8 Auditing Configuration Changes Across NetScaler Devices ... .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .55Configuring Audit Templates .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Configuring Audit Policies .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Generating Audit Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

9 Using Performance Reports and Thresholds to Monitor Device Performance . . . . . . . . . . . . . . . . .59Configuring Polled Counters... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Running Quick Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Configuring Custom Reports.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61

Using Built- in Custom Reports..........................................................62

Adding Custom Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62Viewing Custom Reports.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63

Scheduling Custom Reports.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63

Configuring Thresholds to Monitor Devices... .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 63

Monitoring AppFirewall Syslog Events.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .64

Using the Dashboard... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65

Scheduling the Dashboard View........................................................65

To schedule the dashboard view.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 65

Citrix Command Center User's Guide

v


6/220

Using Repor ts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66

Viewing Recent Log Messages.........................................................66Configuring Views.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67

Searching Recent AppFirewall Log Messages... .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..67

10 NetScaler SNMP Counters Polled from Command Center... .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .69

AAA Counters.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71

ACL Counters.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77

ACL Table Counters.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78

ACL6 Counters.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79

ACL6 Table Counters.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81

Application Firewall Counters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82Cache Redirection Policies Counters.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..89

Compression Counters... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89

Content Fi l ters Counters... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94

Content Switch Policies Counters...........................................................94

CPU Usage Counters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96

DNS Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97

GSLB Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101

HTTP Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102

ICMP Counters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111

Integrated Cache Counters.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114

Interface Counters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139

IP Counters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .143

Policy Engine Counters.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .147

Resources Counters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .148

Service Groups Counters.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .148

Services Counters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .154

Simple ACL Counters... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .159

SSL Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .161

Sure Connect Counters.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .180

System Disk Counters... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .184

TCP Counters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .186

UDP Counters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .194

Virtual Services Counters... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .198

VLAN Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .199

VPN Counters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .204

Virtual Servers Counters.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .213

Contents

vi


7/220

Preface

Learn about the Command Center documentation, including information about supportoptions and ways to send us feedback.

For information about new features and enhancements for this release, see the CitrixCommand Center 4.1 Release Notes.

Formatting ConventionsThis documentation uses the following formatting conventions.

Convention Meaning

Boldface Information that you type exactly asshown (user input); elements in the userinterface.

Italics Placeholders for information orparameters that you provide. Forexample, FileName in a command meansyou type the actual name of a file. Also,new terms, and words referred to aswords (which would otherwise be

enclosed in quotation marks).

Monospace System output or characters in acommand line. User input andplaceholders also are formatted usingmonspace text.

Related DocumentationCitrix documentation is available at http://support.citrix.com/.

For information about Citrix Command Center, the following guides are available:

w Citrix Command Center Installation Guide. Installation instructions for installingCommand Center on Windows and Linux platforms.

w Citrix Command Center Administrator's Guide. Conceptual reference andinstructions for administering, securing, and backing up the CommandCenter server.

w Citrix Command Center User's Guide. Conceptual reference for managingandmonitoring NetScaler and WANScaler devices using Command Center.

7
http://support.citrix.com/http://support.citrix.com/


8/220

w Citrix Command Center Release Notes. Up-to-date information about new featuresand known issues.

Note: Citrix Command Center documentation is also available at: http://docs.citrix.com.

For information about the Citrix NetScaler, the following guides are available:

w Citrix NetScaler Quick Start Guide. Quick reference for basic hardware and softwareinstallation.

w Citrix Hardware Installation and Setup Guide. Hardware installation and initialconfiguration information for all hardware models and platforms.

w Citrix NetScaler Getting Started Guide. Core concepts, installation, andconfiguration instructions for setting up a NetScaler for the first time. Includes hands-on labs that covers commonly used features.

w Citrix NetScaler Migration Guide. Migration instructions for setting up a new versionof a NetScaler with a list of all new and deprecated commands, parameters, andSNMP OIDs.

w Citrix NetScaler Administration Guide. Manage and monitor the NetScaler using built-in features, such as AAA policies, role-based authorization, SNMP, and statisticalcounters.

w Citrix NetScaler Traffic Management Guide. Configuration and installationinformation for traffic management features, such as load balancing, contentswitching, and DNS.

w Citrix NetScaler Application Optimization Guide. Configuration and installation

information for optimization features, such as integrated caching and TCP buffering.Most optimization features are policy-based.

w Citrix NetScaler Application Security Guide. Configuration and installationinformation for security features, such as Denial of Service (DoS) protection,content filtering, and rewrite.

w Citrix NetScaler Networking Guide. Configuration information for networkingfeatures with an emphasis on dynamic routing.

w Citrix NetScaler Policy Configuration and Reference Guide. Configuration andreference information for controlling the behavior of NetScaler functions by usingadvanced policies and expressions, classic policies and expressions, and HTTP callouts.

w Citrix Application Firewall Guide. Installation and configuration instructions for astandalone Citrix Application Firewall and the integrated Citrix NetScalerApplication Firewall feature.

w Citrix NetScaler Developers Guide. A guide for application developers who use XMLAPI.

w Citrix NetScaler API Reference. A reference guide for application developers.

w Citrix NetScaler Command Reference Guide. A reference that includes all NetScalercommands.

Preface

8
http://docs.citrix.com/http://docs.citrix.com/


9/220

w Citrix NetScaler Log Message Reference. A reference that includes syslog and Webserver log messages.

w Citrix NetScaler SNMP OID Reference. A reference that includes Simple Network

Management Protocol (SNMP) object identifiers for objects in the ManagementInformation Base (MIB).

w Citrix NetScaler Release Notes. Up-to-date information about new features andknown issues.

For information about Citrix Access Gateway Enterprise Edition, the following guidesare available:

w Citrix Access Gateway Enterprise Edition Pre-Installation Checklist. Planninginformation and task checklists for installing the Access Gateway

w Getting Started with Citrix Access Gateway Enterprise Edition. Installation andconfiguration instructions for setting up the Access Gateway for the first time.

w Citrix Access Gateway Enterprise Edition Administrators Guide. Installation andconfiguration instructions for all the Access Gateway features.

w Citrix Access Gateway Plugin for Windows User Guide. Installation, configuration,and troubleshooting information for day-to-day use of the Access Gateway Plugin forWindows.

w Citrix Access Gateway Plugin for Java User Guide. Installation, configuration, andtroubleshooting information for day-to-day use of the Access Gateway Plugin for Java.

w Citrix Secure Gateway to Access Gateway Migration Guide. Migration and upgradeinformation for moving from Secure Gateway to Access Gateway.

w Citrix Access Gateway Enterprise Edition Integration Guide for Citrix XenApp and

Citrix XenDesktop. Installation and configuration information for integrating theAccess Gateway, Citrix XenApp and Citrix XenDesktop systems. Also, includesinformation about migrating from the Secure Gateway to Access Gateway.

w Citrix Access Gateway Readme. Up-to-date information about known issues.

For information about Citrix Branch Repeater system, the following guides are available:

w Citrix Branch Repeater Family Client and Appliance Installation Guide. Installationinstructions for installing the Branch Repeater family client and appliance.

w Branch Repeater Family Release Notes. Up-to-date information about new featuresand known issues.

Getting Service and SupportCitrix offers the following support options for Command Center.

Knowledge Center

The Knowledge Center offers a variety of self-service, Web-based technical supporttools at http://support.citrix.com/.

Knowledge Center features include:


9
http://support.citrix.com/


10/220

w A knowledge base containing thousands of technical solutions to support your Citrixenvironment

w An online product documentation library

w Interactive support forums for every Citrix product

w Access to the latest hotfixes and service packs

w Knowledge Center Alerts that notify you when a topic is updated

Note: To set up an alert, sign in at http://support.citrix.com/and, under Products,

select a specific product. In the upper-right section of the screen, under Tools, click

Add to your Hotfix Alerts. To remove an alert, go to the Knowledge Center

product and, under Tools, click Remove from your Hotfix Alerts.

w Security bulletins

w Online problem reporting and tracking (for organizations with valid support contracts)

Education and Training

Citrix offers a variety of instructor-led and Web-based training solutions. Instructor-ledcourses are offered through Citrix Authorized Learning Centers (CALCs). CALCs providehigh-quality classroom learning using professional courseware developed by Citrix.Many of these courses lead to certification.

Web-based training courses are available through CALCs, resellers, and from the CitrixWeb site.

Information about programs and courseware for Citrix training and certification isavailable at http://www.citrixtraining.com.

Documentation FeedbackYou are encouraged to provide feedback and suggestions so that we can enhance thedocumentation. You can provide feedback by sending email [email protected] with the subject line "Documentation Feedback". Be sureto include the following information in your email: title of the guide, page number, andCommand Center release version.

You can also provide feedback from the Knowledge Center at http://support.citrix.com/.

To provide feedback from the Knowledge Center home page

1. Go to the Knowledge Center home page at http://support.citrix.com/.

2. On the Knowledge Centerhome page, in the left pane, under Products, clickView All Products.

3. On the All Productspage, under Command Center, click the version of CommandCenter that has the documentation for which you want to provide feedback.

Preface

10
http://support.citrix.com/http://support.citrix.com/http://www.citrixtraining.com/http://www.citrixtraining.com/http://support.citrix.com/http://support.citrix.com/http://support.citrix.com/http://www.citrixtraining.com/http://support.citrix.com/


11/220

4. On the Documentationtab, click the guide name, and then click Article Feedback.

5. On the Documentation Feedbackpage, complete the form and click Submit.


11


12/220

Preface

12


13/220

Chapter 1

Getting Started with Command Center

Topics:

Logging on to Command

Center

Adding Devices

Understanding the Discovery

Process

Provisioning NetScaler VPX

Devices on XenServers

Viewing the Discovery Status

of Devices

Viewing Inaccessible Devices

Citrix Command Center is a management and monitoringsolution for Citrix application networking products thatinclude Citrix NetScaler, Citrix NetScaler VPX, Citrix AccessGateway Enterprise Edition, Citrix Branch Repeater, CitrixBranch Repeater VPX, and Citrix Repeater. Use CommandCenter to manage, monitor, and troubleshoot the entire globalapplication delivery infrastructure from a single, unifiedconsole.

This centralized management solution simplifies operations byproviding administrators with enterprise-wide visibility andautomating management tasks that need to be executedacross multiple devices.

To begin monitoring and managing Citrix devices, you need toconnect to the Command Center server by using the HTMLWeb client, and then add the devices for discovery. CommandCenter initiates the discovery process, which stores device-related information in the Command Center server.

13


14/220

Logging on to Command CenterYou need to connect to the Command Center server by using the HTML Web client.

To log on to Command Center

1. In your Web browser address field, type one of the following:

http://ComputerName:PortNumberorhttps:///ComputerName:PortNumber

Where:

ComputerNameis the fully qualified domain name (FQDN), host name, or the IPaddress of the Command Center server.

PortNumberis the port used by the Command Center client and server tocommunicate with each other. The default port number for HTTP is 9090 andfor HTTPS is 8443.

2. On the Loginpage, in User Nameand Password, type the user name and passwordto connect to the Command Center server, and then click Login.

The default user name and password are rootand public. However, Citrixrecommends that you change the password after you install the Command Centerserver. For information about changing the root password, see the Citrix CommandCenter 4.1 Administrator's Guide.

The Command Center Home page appears that provides you with a high-level viewof the performance of the Citrix devices that you are managing and monitoring.

On first log on, the Home page does not display any data because you do not haveany Citrix devices discovered on your Command Center.

3. In the Start inlist, select how you want to log on to Command Center. Theavailable options are Home, Citrix Network, Fault, Monitoring, Configuration, andReporting. For example, if you want Command Center to display the Configurationpage when you log on, select Configurationin the Start inlist.

4. In Timeout, type the length of time (in minutes, hours, or days) for which thesession can be inactive before you must log in again. The timeout duration thatyou specify here is applicable only for this client.

You can also specify timeout duration for all the users on the Access Settingspage(Administration> Access Settings). For more information, see "Configuring AccessSettings" in the Citrix Command Center 4.1 Administrator's Guide.

Note: You must minimize the Alarm Summary table for the session timeout to

work. If the Alarm Summary table is expanded, the session is considered to be

active.

5. Click Loginto log in to the Command Center client.

Chapter 1 Getting Started with Command Center

14


15/220

Adding DevicesDevices are Citrix systems that you want to discover and manage.

The devices are represented as icons in the right pane. Different icons depict thedifferent types of devices. NSdepicts NetScaler, AGdepicts AGEE, NS VPXdepictsNetScaler VPX, Rdepicts Repeaters, BRdepicts Branch Repeaters, BRalso depictsBranch Repeaters VPX, and Xdepicts XenServer devices. Different notations, such asgreen, red, and yellow arrows depict the state of the device. Further, HA(highavailability), P(primary), and S(secondary) depict the mode of the device.

The Command Center server supports two types of devices based on their state:

w Standalone : A standalone device functions independently and is not configured inan HA setup.

w HA pair : This represents a pair of devices configured in an HA setup. The primarydevice in an HA setup processes the traffic. The secondary device monitors theprimary and takes over the functions of the primary device if that device is unableto continue processing traffic.

You can add devices by specifying the host names of the devices, the IP addresses ofeach device, a range of IP addresses, and NAT HA devices. You can also add devices byimporting the device names from a file. Note that when you specify a range, the firstthree octets of the low and high addresses must be the same. Command Centerdiscovers only 254 devices using an IP address range.

For information on the procedure to add devices, do the following:

w Click Helpfrom the Command Center client.

Understanding the Discovery ProcessCommand Center initiates the discovery process when you add the devices to the map.Command Center discovers devices based on the user credentials and/or the hostnames and IP addresses that you provide when adding a map or device.

After you initiate the discovery process, the device goes through a series of steps. Eachstep and its status in the discovery process are visible in Command Center. To view thediscovery status, see the section "Viewing the Discovery Status of Devices.".

The Command Center discovery process involves the following steps:

1. SNMP ping:The Command Center server sends a Simple Network ManagementProtocol (SNMP) GET request to a Citrix system-specific object identifier (OID) (forexample, 1.3.6.1.4.1.5951.1.1). If the server successfully pings the device, it setsthe status of step 2 to SUCCESS and proceeds to step 3. If the GET request fails,the device is not a Citrix device, or it is a Citrix device but SNMP is disabled on it.In either fail case, the Command Center server proceeds to step 2.

2. Find Citrix device: The Command Center server attempts to open an SSH sessionto the device based on the user credentials configured when adding a map. If the


15


16/220

SSH session fails, the device is discarded as a non-Citrix device. If the SSH sessionsucceeds, the server issues a CLI command to check whether the device is a Citrixdevice. A positive result moves the device to the next step. Otherwise, Command

Center discards the device as a non-Citrix device. To check the cause of failure ofthis step, on the Citrix Networktab, click the >>>icon next to the device, andselect Status. You can also view the cause of failure on the Device Statuspage.

3. Enable SNMP:On the discovered Citrix device, Command Center executes acommand to configure an SNMP community based on the details entered whenconfiguring the map or when adding a device. This step may fail for variousreasons, such as network issues or if another SNMP manager is already configuredon the device. To check the cause of failure, on the Citrix Networktab, click the>>>icon next to the device, and select Status. You can also view the cause offailure on the Device Statuspage.

4. Add trap destination: Devices communicate with Command Center by sending trapnotifications. The Command Center server adds its IP address to the list of trap

destinations on the discovered device. This allows Command Center to receive allevents/traps generated on the Citrix device. However, this step may fail if thenumber of trap destinations exceeds the maximum limit of trap destinations on theCitrix device. The limit on Citrix NetScaler devices is 10. If an error occurs youmust take corrective measures before you initiate rediscovery of this device. Tocheck the cause of failure, on the Citrix Networktab, click the >>>icon next tothe device, and select Status.You can also view the cause of failure on theDeviceStatuspage.

Note: If Command Center is behind a Network Address Translation (NAT) device,

the trap destination configured on the server is its internal IP, and the events and

traps generated by the Citrix device do not reach the Command Center server. To

set the trap destination in this case, you must configure it from theAdministrationtab. For more information, see Setting Up an SNMP Trap

Destination in the Citrix Command Center Administrators Guide.

5. Collect inventory:The Command Center server collects the basic systeminformation for the discovered devices using SNMP. You can view this informationon the Device Properties page. For more information, see Viewing DeviceProperties in the Citrix Command Center Online Help. This step may fail if theSNMP manager configured on the Citrix device is not that of the server. It may alsofail because of network issues or because the SNMP ports are not configuredproperly on the firewall. To check the cause of failure, on the Citrix Networktab,click the >>>icon next to the device, and select Status. You can also view thecause of failure on the Device Statuspage. If an error occurs you must take

corrective measures, and then initiate rediscovery of the device.

6. Download files: The Command Center server initiates a Secure File TransferProtocol (SFTP) session based on the user credentials defined while configuring themap. Then, it downloads the configuration and license files of the device. ForRepeater devices, it downloads only the configuration files. The Command Centerserver stores these files in the database. This step may fail because of thefollowing reasons:

Incorrectly specified user credentials


16


17/220

Incorrectly configured SFTP ports in the firewall

Network issues

To check the cause of failure, on the Citrix Networktab, click the >>>icon nextto the device, and select Status. You can also view the cause of failure on theDevice Statuspage. If an error occurs, you must take corrective measures, andthen initiate rediscovery of this device.

Note: If the discovery process fails, the failed step is marked as FAILED. Any

subsequent steps are marked as N/A.

Upon successful discovery, the devices appear on the corresponding maps as icons withtheir IP addresses or device names. If the server is unable to successfully discover thedevices, it marks the devices as inaccessible, generates an event, and groups thedevices under the Inaccessible Systemsnode.

Provisioning NetScaler VPX Devices onXenServers

Using Command Center you can provision NetScaler VPX on XenServers and beginmanaging the NetScaler VPX instances.

You can install one or more instances of NetScaler VPX on a XenServer from theCommand Center client by using a NetScaler VPX template. The number of instancesthat you can install depends on the amount of memory available on the hardware thatis running XenServer.

To provision NetScaler VPX on a XenServer, first, you need to add the XenServer deviceand set it for discovery. After the XenServer is discovered, you can provision theNetScaler VPX devices on the XenServer from the Command Center client. CommandCenter implicitly deploys NetScaler VPX devices on the XenServer, and then discoversthe NetScaler VPX devices for monitoring and management.

Important: Before you begin provisioning the NetScaler VPX devices, create a

NetScaler VPX template on the XenServer. Make sure that the template name

contains the word "NetScaler" as part of the name string, for example, "NetScaler

Virtual Appliance". Command Center recognizes only template names with "NetScaler"

in the string as NetScaler VPX templates.

When you provision NetScaler VPX from Command Center, you need to provide valuesfor the following parameters, and Command Center implicitly configures these settingson the NetScaler VPX.

w NetScaler IP address (NSIP): Specifies the IP address at which you access aNetScaler VPX instance for management purposes. A NetScaler VPX can have onlyone NSIP. You cannot remove an NSIP address.

w Netmask: Specifies the subnet mask associated with the NSIP address.


17


18/220

w Gateway: Specifes the default gateway that you must add on the NetScaler VPX ifyou want access through SSH or the configuration utility from an administrativeworkstation or laptop that is on a different network.

For information on the procedure to provision NetScaler VPX devices on XenServer, doone of the following:


Viewing the Discovery Status of DevicesCommand Center lets you view the discovery status of all discovered as well asinaccessible devices.

You can view the following details:

w Time: Time when the step in the discovery process started.

w Device: Device that is being discovered.

w Step: Step in the discovery process that is executed, such as add trap destinationand enable SNMP.

w Status: Status of a step in the discovery process. The status can be STARTED,COMPLETED, and FAILED.

w Message: Message that describes the reason of the discovery process failure or thedetails of when the discovery process started on a particular device.

Viewing Inaccessible DevicesWhen any step of the discovery process fails either when adding a new device or whenrediscovering an existing device, Command Center moves the device to theInaccessible Systemsnode and notifies the administrator through an event.Subsequent successful rediscovery of the device makes it available for monitoring andmanaging.

You can perform a set of tasks on inaccessible devices, such as viewing the deviceproperties and status, invoking the configuration utility and CLI, and rediscovering thedevice.


18


19/220

Chapter 2

Monitoring the Citrix Network

Topics:

Configuring Maps

Configuring NetScaler Pool

Monitoring Two-Tier

Application View

Monitoring Datacenter View

Monitoring Devices

Citrix network comprises devices or Citrix systems that youwant to discover and manage. To begin monitoring andmanaging devices, you need to add the devices to yourCommand Center, which sets them for discovery.

After devices are discovered, you can group them underlogical containers called maps, or you can create NetScalerpools that represent a group of devices considered as a single

logical unit. The devices are further grouped based on theirlocation values and you can monitor the devices using theDatacenterpane.

You can also monitor applications configured on NetScalerdevices set up in a two-tier architecture.

19


20/220

Configuring MapsMaps are logical containers that either graphically represent a group of discoveredCitrix devices, or represent a group of devices configured as a NetScaler pool and areconsidered a single logical unit. When adding a map, you need to select the devicesyou want to grouped under that map. After adding a map, you can perform operationson a map, such as adding submaps and modifying maps. You can also performoperations on all the devices in a map, such as configuring audit and running reports.

In this section:

w Adding Mapson page 20

w Adding Submapson page 20

w Performing Operations on Mapson page 20

Adding MapsMaps are logical containers that either graphically represent a group of discoveredCitrix devices, or represent a group of devices configured as a NetScaler pool and areconsidered a single logical unit.

You can either add a map and group devices under it logically, such as based onfeatures configured on your devices.

Or, you can add a NetScaler pool and add devices to it. The devices added in mapsconfigured as NetScaler pools are considered one logical unit. All configuration changesare done on all the devices in a pool. After adding a NetScaler pool, you need toconfigure VIPs on the pool. Note that if you have a NetScaler pool already configuredon your network, you only need to add the devices that are part of the pool.

Note: For more information on how NetScaler pools work, see the Citrix NetScaler

Networking Guide

For information on the procedure to add maps and NetScaler pools, do the following:


Adding SubmapsYou can add submaps within existing maps. Submaps let you logically group the devicesdiscovered on a map. For example, you may want to configure a submap based on thegeographical location of your devices. By default, when a submap is created under amap, it inherits the properties of the parent map.

Performing Operations on MapsAfter you have grouped devices by adding maps or NetScaler pools , you can perform aset of operations on all the devices grouped under a specific map or pool:

Chapter 2 Monitoring the Citrix Network

20


21/220

w Add SubMap: Add submaps within existing maps. You cannot create a submap withina pool.

w Modify: Modify the map to add or remove devices, or if the device login credentials

and SNMP version details have changed. You cannot modify a pool.

w Run Report: Run a custom report on all the devices in a map or a pool totroubleshoot or analyze the behavior of the devices.

w Execute Task: Execute a built-in or custom task on all the devices in a map or a pool.

w Config Audit: Run configuration audits on all the devices in a map or a pool tomonitor configuration changes across the devices.

w Configure NS Pool: Configure the NetScaler pool by adding VIPs.

w NS Pool Dashboard: View the configured VIP status across all the devices in a pool.

w Rediscover: Rediscover all the devices in a map or a pool.

w Delete: Delete all the devices from the map or pool.

w Discovery Status: View the discovery status of all the devices.

For information on the procedures to perform these operations, do the following:


Configuring NetScaler PoolA map configured as a NetScaler pool consists of devices that are considered as onelogical unit. All configuration changes are done on all the devices in a pool.

You may have a NetScaler pool already configured on your network; in which case, youneed to add the devices that are part of the pool when adding the map.

Or, you may configure a NetScaler pool from Command Center. In this case, add thedevices that you want to be part of the pool when adding the map. These devices aredisplayed as a single unit in the Mapspane. After you have added a NetScaler pool andadded devices to it , you need to configure the NetScaler pool by adding VIPs to it.After you have added the VIP addresses, Command Center implicitly configures theseVIPs across all the NetScaler devices added to the pool. Command Center furtherassigns priorities to these VIPs to set up a distributed VIP configuration.

Note: For more information on how NetScaler pools work, see the Citrix NetScaler

Networking Guide.

For information on the procedure to configure NetScaler pools, do he following:


Viewing the NetScaler Pool DashboardAfter Command Center configures the VIPs across all the NetScaler devices added to apool, you can view the configured VIP status across all the NetScaler devices in that


21


22/220

pool. The NS Pool Dashboardprovides a tabular view of the VIPs assigned to theNetScaler devices based on the priorities assigned to the VIPs. The active VIPs aredepicted by a green icon.

Performing Operations on NetScaler PoolYou can also perform various operations on a NetScaler pool, such as run a report andexecute a task. When you perform an operation on a pool, the operation is performedon all the devices in the pool. If an operation, such as executing a configuration, failson one of the devices in the pool, the configuration is rolled back on all the otherdevices where it has been successfully executed.

For information on the procedures to perform operations on pools, do the following:


Monitoring Two-Tier Application ViewYou can view and monitor applications configured on NetScaler devices set up in a two-tier architecture.

Consider that you have configured a load balancing virtual on a NetScaler device intier-1, which is the Flex tier. And you have three NetScaler VPX devices with loadbalancing virtual servers configured in tier-2, which is the application tier. Now, on theNetScaler in tier-1 (Flex tier), configure and bind services that represent the virtualservers on your NetScaler VPX devices in tier-2 (App tier).

Using Command Center you can view and monitor the devices and the entitiesconfigured in this topology.

You can view the following details about the applications:

w Application Name: Specifes the name of the application that you have configured inthe two-tier toplogy. Clicking the application name displays the IP addresses of thedevices and the endpoints configured in your setup.

w Flex Tier: Specifies the number of devices configured in the Flex tier (tier-1).Clicking this number displays the details of the devices configured in this tier.

w App Tier: Specifes the number of devices configured in the App tier (tier-2).Clicking this number displays the details of the devices configured in this tier.

w Refresh: Retrieves latest data from the devices configured in the two-tier topology.

For each application, you can also view the following:

w Under Flex Tier, view the IP address of the device configured in this tier. Also, viewthe endpoint configured. This is the public endpoint and specifies how users accessan application. It receives all of the traffic from a client that pertains to aparticular application. The endpoint is represented as IP:Port combination, forexample, 6.6.6.13:443.

w Under App Tier, view the IP address of the devices configured in this tier. Also, viewthe endpoints configured. These endpoints are accessed by the services configured


22


23/220

on the NetScaler device in Flex tier. The endpoint is represented as IP:Portcombination, for example, 1.1.1.132:80.

For information on the procedure to view and monitor the applications, do the following:


Monitoring Datacenter ViewThe Datacenter pane groups the discovered Citrix devices based on the locationconfigured on these devices. For example, if you configure the Location value of a setof devices as Santa Clara, Command Center groups these devices within the SantaClaragroup. Further if you change the Location value of a device, Command Center regroupsthe device on subsequent rediscovery of the device.

You can perform the following operations on the devices in these groups:

w Run Report: Run a custom report of any polled counters to troubleshoot or analyzethe behavior of a device.

w Execute Task: Execute built-in and custom tasks to make configuration changesacross devices.

w Config Audit : Run configuration audits on the devices to monitor configurationchanges across managed devices and troubleshoot configuration errors.

To perform these operations, click the >>>icon next to a group, and then click theoperation you want to run.

Monitoring DevicesAfter the devices are discovered, you can perform various operations specific to singledevices or multiple devices on the Citrix Networktab.

The NeScaler family of devices include NetScaler (depicted by the NSicon), AccessGateway (depicted by the AGicon), and NetScaler VPX (depicted by the NS VPXicon)devices. The Repeater family of devices include Repeater (depicted by the Ricon) andBranch Repeater and Branch Repeater VPX (both depicted by the BRicon) devices.

You can perform the following operations to monitor single or multiple devices.

w Viewing Device Properties: During every discovery or rediscovery of a device,

Command Center downloads and stores the configuration and license files of thatdevice. These files contain device-related information that you can view in deviceproperties.

w Running Reports: Run a custom report of any polled counters to troubleshoot oranalyze the behavior of a device.

w Viewing Events and Alarms: When the IP address of the Command Center server isadded to the list of trap destinations on a discovered device, the device routes all


23


24/220

events or traps to Command Center. From the Citrix Network tab, you can view theevents and alarms for single devices.

w Executing Tasks: Execute built-in and custom tasks on single or multiple devices tosimplify device management and minimize configuration errors.

w Running Configuration Audits: Run configuration audits on Citrix devices to monitorconfiguration changes across managed NetScaler devices, troubleshoot configurationerrors, and recover unsaved configurations upon a sudden system shutdown.

w Invoking the CLI of NetScaler Devices: Launch the Citrix NetScaler CLI for aselected NetScaler device.

w Invoking the User Interface of NetScaler Devices: Launch the browser-basedNetScaler user interface for a selected device. You can use the user interface tolaunch the configuration utility, dashboard, monitoring, and reporting tools of anyNetScaler device.

w Invoking the CLI and User Interface of Repeater Devices: Launch the CitrixRepeater CLI and user interface for a selected Repeater device.

w Generating the Tar Archive of Configuration Data of NetScaler Devices: Use theShow TechSupport option to generate a tar archive of system configuration data andstatistics for submission to Citrix technical support.

w Replicating a Repeater Device's Configuration to Other Repeater Devices:Replicate the configuration of a Repeater device to multiple Repeater devices onyour network to save time and minimize configuration errors.

w Viewing the Replication Status of Repeater Devices: View the status of aconfiguration that has been replicated from a Repeater device to one or moreRepeater devices.

w Viewing the Device Configuration of Repeater Devices: View the runningconfiguration of standalone and high availability (HA) primary Repeater devices.

w Searching Devices from Device Inventory: Search for any discovered NetScaler,NetScaler VPX, Access Gateway, Branch Repeater, Repeater, Branch Repeater VPX,or Xen Server device on your Citrix network.

w Configuring the Location: Configure or modify the location value of a device.

w Restarting Devices: Restart a device after performing tasks such as changing theconfiguration or upgrading the system.

w Pinging Devices: ping a device to check whether the device is reachable from theCommand Center server.

w Tracing the Route of Devices: Trace the route of a packet from the server to adevice through a network by determining the number of hops necessary to reach thedevice.

w Viewing the Discovery Status: View the discovery status of a device. You can viewthe step that has failed and the reason why the step has failed.


24


25/220

w Rediscovering Devices: Rediscover devices to view the latest state of the deviceand its configuration file, or to set a device for rediscovery if the device has movedto the Inaccessible Systems node.

w Moving Devices to Another Map: Move a discovered device from one map to another.

w Deleting Devices: Delete a device if you do not want to manage or monitor it.Deleting a device permanently removes the device and its related details from thedatabase of the Command Center server.

w Unmanaging Devices: Stop managing a device and stop the exchange of informationbetween the device and the Command Center server.

w Performing Operations Specific to HA Devices: Perform a set of operations specificto the HA devices, such as forcing a failover and forcing a secondary to stay as asecondary.

For information on the procedures to perform these operations, do the following:



25


26/220


26


27/220

Chapter 3

Monitoring Your Network by Using theHome Page

Topics:

Understanding the Alarm

Summary

Monitoring Device Inventory

Monitoring Active Alarms

Monitoring Recent Alarms

Finding Devices

The Command Center Home page provides you with a high-level view of the performance of your Citrix network. TheHome page contains graphical and tabular representation ofthe following statistics about your devices on the network:

w Alarm Summary: An aggregate view of the alarms for all of

the discovered devices in your network.

w Device Inventory: Summary of alarm status for eachdevice category, such as NetScaler or Access Gateway.

w Active Alarms: Graphical representation of the number ofcurrently active alarms by their severity.

w My Assignments: List of alarms assigned to you. You maypick up alarms to resolve them, or you may unpick thealarms and assign them to other users.

w Recent Alarms: A list of the five most recent alarms withdetails, such as date or time, severity, category, source of

alarm (system IP address), and description.

27


28/220

Understanding the Alarm SummaryThe Alarm Summary table is an aggregate view of the alarms for all the discovereddevices on your network. This aggregate is based on the categories and severity of thealarms. The table is updated automatically.

The alarm details include the date and time the alarms was generated, the severity,and the actions.

For information about the color codes of the alarms, see Monitoring Active Alarms onpage 29.

To view the alarm details for a particularcategory of alarms, click the category namein the table. On the Alarms page, you can view the following details:

w Date/Time: Specifies the date and time when the alarm was generated.

w Severity: Specifies the severity of the alarm, such as Major and Warning.

w Actions: Specifies the actions you can take on the alarms. The possible actions areAlarm Pickup and Annotate.

w Category: Specifies the alarm category, for example, vserverTxBytesRate.

w Source: Specifies the system name, host name, or the IP address of the device onwhich the alarm is generated.

w Failure Object: Specifies the object on which the alarm is raised.

w Description: Specifies the description of the alarm.

Monitoring Device InventoryThe Inventory view is a table listing the device types and the alarm status of all deviceson the network. It also displays the total number of devices (discovered andinaccessible) managed by Command Center.

w The first column lists the device types and the number of discovered andinaccessible devices for each device type. The device types listed are: NetScaler(NS), NetScaler VPX (NS VPX), Access Gateway (AG), Repeater (R), and BranchRepeater (BR), and XenServer (X). Clicking the device type displays the details of allthe devices in that category.

w

The second through sixth columns display the number of devices (for each devicetype) with the alarm severity depicted by the alarm color code. For information onalarm color code, see Monitoring Active Alarms on page 29. Clicking any of thenumbers in these columns displays the details of devices with pending alarms or nopending alarms, as is applicable.

w The last column displays the number of inaccessible devices for each device type.Clicking a number in the last column displays the inaccessible devices for thecorresponding category.

On clicking any of the columns, you can view the following details of the devices:

Chapter 3 Monitoring Your Network by Using the Home Page

28


29/220


30/220


31/220

Chapter 4

Monitoring and Managing EventsGenerated on Citrix Devices

Topics:

Monitoring SNMP Events and

Alarms

Managing SNMP Events and

Alarms

Monitoring Syslog Events

Configuring Event and Alarm

Triggers

Use the Fault tab in Command Center to monitor and managethe SNMP and syslog events generated on the Citrix devices.Command Center identifies errors or events based on the real-time status of the devices. It further generates alarms for theidentified events, thereby helping administrators to addressissues immediately and keep the network running effectively.You can also configure event triggers to filter the eventsgenerated by Command Center and take actions on thefiltered list of events.

For information about NetScaler SNMP OIDs, traps, and systemhealth counters, see the Citrix NetScaler SNMP OID Referenceat: http://support.citrix.com/article/CTX128676.

For information about NetScaler Syslog messages, see theCitrix NetScaler Log Message Reference at: http://support.citrix.com/article/CTX128679.

31
http://support.citrix.com/article/CTX128679http://support.citrix.com/article/CTX128679http://support.citrix.com/article/CTX128676


32/220

Monitoring SNMP Events and AlarmsWhen the Command Center server adds its IP address to the list of trap destinations ona discovered device, the device routes all events or traps generated on it to CommandCenter. From these SNMP trap notifications, the Command Center server automaticallyconsolidates a list of the events that occur on the discovered devices.

Command Center correlates the history of events to form alarms of different severitylevels and displays them as messages, some of which may require immediate attention.The alarms are correlated for similar kinds of events. For example, for events linkUpand linkDown of the same entity Linkoccurring in the same device, only one alarm isgenerated, stating the latest status and the severity of the event.

Each event stored in Command Center occupies approximately 250 bytes of space.Command Center stores the events of six months and displays only the latest 10,000

events and alarms.

For information about NetScaler SNMP OIDs, traps, and system health counters, seeNetScaler SNMP OID Reference.

Viewing EventsEvents represent occurrences of events or errors on Citrix devices. For example, whena failure or fault is detected on a Citrix device, an event occurs. The Command Centerserver collects information about these events.

You can view the following details about events:

w Severity: Specifies the severity of the event, such as critical, major, warning, minor,or clear.

w Source: Specifies the IP address, the system name, or the host name of the deviceon which the event is generated.

w Date: Specifies the date and time when the event was generated. The date formatis MMM DD, YYYY HH:MM:SSAM/PM.

w Category: Specifies the category of the device to which the event belongs, such asdiscovery standalone, inaccessible system, or a discovery HA pair.

w Message: Specifies the message associated with the event, such as "Command: savens config Authorization Status: AUTHORIZED Result: SUCCESS User: nsroot."

For SNMP authentication failures, the message also displays the IP address of the

device that failed authentication.

w Device Type: Specifies the type of the device, such as NetScaler or Repeater.

Viewing AlarmsCommand Center correlates the history of events to form alarms of different severitylevels and displays them as messages, some of which may require immediate attention.The alarms are correlated for similar kinds of events. For example, for events linkUp

Chapter 4 Monitoring and Managing Events Generated on Citrix Devices

32
http://support.citrix.com/article/CTX121833http://support.citrix.com/article/CTX121833


33/220

and linkDown of the same entity Linkoccurring in the same device, only one alarm isgenerated, stating the latest status and the severity of the event.

You can view either all the alarms for all the events, or view the alarm associated withan event.

You can view the following details about alarms:

w Date/Time: Specifies the date and time when the alarm was generated (that is, thelatest time of the occurrence of the event associated with the alarm). The date/time format is MM DD, YYYY HH:MM:SS AM/PM.

w Severity: Specifies the current severity of the alarmcritical, major, minor, warning,info, or clear.

w Actions: Specifies the permitted actions (for example, annotate and pickup) thatyou can perform on the alarm.

w

Category: Specifies the type of alarm (for example, Entitydown or linkDown).w Source: Specifies the IP address ,the system name, or thehost name of the device

on which the events that caused the alarm occurred.

w Failure Object: Specifies the object that triggered the alarm (for example, entity).

w Description: Specifies the properties (for example, alarm creation date, lastupdated date, and current and previous severity) of the alarm, with a detailedmessage.

Configuring Views for Events and Alarms

You can configure views to monitor specific events and alarms based on the criteria youspecify.

Views make it easier to monitor a large number of events generated across yourNetScaler infrastructure. For example, you can create a view to monitor all majorevents raised when there is a high CPU usage.

For information on the procedures to configure events and alarms, do one of thefollowing:


w See Command Center documentation at: http://support.citrix.com/proddocs/topic/netscaler/cc-gen-command-center40-wrapper-con.html

Managing SNMP Events and AlarmsYou can manage the events generated on all your devices from the Command Centerconsole. You can set a time interval for which you want Command Center to poll theevents. You can assign alarms to Command Center users to analyze and resolve them.You can also print the list of events and alarms for analysis, or save the list of eventsand alarms to a file on your local system.


33
http://support.citrix.com/proddocs/topic/netscaler/cc-gen-command-center40-wrapper-con.htmlhttp://support.citrix.com/proddocs/topic/netscaler/cc-gen-command-center40-wrapper-con.htmlhttp://support.citrix.com/proddocs/topic/netscaler/cc-gen-command-center40-wrapper-con.htmlhttp://support.citrix.com/proddocs/topic/netscaler/cc-gen-command-center40-wrapper-con.html


34/220

For information on the procedures to manage SNMP events and alarms, do one of thefollowing:



Monitoring Syslog EventsYou can monitor the syslog events generated on your NetScaler device if you haveconfigured your device to redirect all syslog messages to the Command Center server.To monitor syslog events, you need to first configure Command Center as the syslogserver for your NetScaler.

For information about NetScaler Syslog messages, see NetScaler Log Message Reference.

Configuring Command Center as the Syslog ServerTo enable Command Center to display syslog messages generated on NetScaler devices,you need to add your Command Center server as the syslog server on the NetScaler device.

To configure Command Center as the syslog server

1. Log on to the NetScaler device

2. To add a syslog action, at the NetScaler command prompt, type:

add audit syslogAction [-serverPort ] -

logLevel ... [-dateFormat ( MMDDYYYY | DDMMYYYY )][-logFacility ] [- tcp ( NONE | ALL )] [-acl( ENABLED | DISABLED )] [- timeZone ( GMT_TIME | LOCAL_TIME )]

Example

add audit syslogAction CC_action 10.102.29.70 -serverPort 514 -logLevel ALL -dateFormat MMDDYYYY -logFacility LOCAL0 - tcpALL -acl DISABLED -timeZone LOCAL_TIME

Note: The value for serverIP should be the IP address of your Command Center

server, and the serverPort should be 514.

3. Add a syslog policy so that all syslog messages are forwarded to the Command

Center server. The policy defines the conditions under which the specified syslogserver will be used for logging. To add a syslog policy, at the NetScaler commandprompt, type:

add audit syslogPolicy

Example

add audit syslogpolicy CC_pol ns_true CC_action

4. To bind the policy globally, at the NetScaler command prompt, type:

bind system global

Chapter 4 Monitoring and Managing Events Generated on Citrix Devices

34
http://support.citrix.com/article/CTX121821http://support.citrix.com/proddocs/topic/netscaler/cc-gen-command-center40-wrapper-con.htmlhttp://support.citrix.com/proddocs/topic/netscaler/cc-gen-command-center40-wrapper-con.html


35/220


36/220


37/220

Chapter 5

Monitoring and Managing the Real-TimeStatus of Entities Configured on NetScaler

Devices

Topics:

Monitoring Virtual Servers,

Services, and Service Groups

Managing the Real-Time

Status of Entities

Use Command Center to monitor and manage the states ofvirtual servers, services, and service groups across theNetScaler infrastructure. You can monitor values, such as the

health of a virtual server and the time elapsed since the laststate change of a service or service group. This gives youvisibility into the real-time status of the entities and makesmanagement of these entities easy when you have a largenumber of entities configured on your NetScaler devices.

37


38/220

Monitoring Virtual Servers, Services, and

Service GroupsYou can monitor the real-time status of virtual servers, services, and service groupsusing the Monitoring feature of Command Center. You can also view the services andservice groups bound to virtual servers.

You can further add views to monitor specific entities based on entity names, devicenames, protocol types, states, and health.

Viewing the Status of Virtual ServersUse Command Center to monitor the real-time values of the state and health of avirtual server. You can also view the attributes of a virtual server, such as name, IPaddress, and type of virtual server.

You can view the following statistics:

w Device Name: Specifies the name of the device on which the virtual server isconfigured.

w Name: Specifies the name of the virtual server.

w IP: Specifies the IP address of the virtual server. Clients send connection requests tothis IP address.

w Port: Specifies the port on which the virtual server listens for client connections.

w Type: Specifies the type of virtual server (for example, load balancing). Thisinformation is available only for virtual servers configured on NetScaler release 9.0and later.

w Protocol: Specifies the service type of the virtual server. For example, HTTP, TCP,and SSL.

w State: Specifies the current state of the virtual server. For example, UP, DOWN, andOUT OF SERVICE.

w Health: Specifies the percentage of the services that are in the state UP and arebound to the virtual server. The following formula is used to calculate the healthpercentage: (Number of bound UP services * 100) / Total bound services

w Last State Change: Specifies the time elapsed (in days, hours, minutes, and seconds)

since the last change in the state of the virtual server, that is, the duration of timefor which the virtual server is in the current state. This information is available onlyfor virtual servers configured on NetScaler release 9.0 and later.

You can monitor the real-time status of the services and service groups bound to avirtual server. This lets you check the state of the services that may cause the healthpercentage of a virtual server to become low, and then you can take appropriate action.

For information on the procedure to view the status of virtual servers, do one of thefollowing:

Chapter 5 Monitoring and Managing the Real-Time Status of Entities Configured on NetScaler Devices

38


39/220



Viewing the Status of ServicesUse Command Center to monitor the real-time values of the state of a service and theduration for which a service is in the current state.

You can view the following statistics:

w Device Name: Specifies the name of the device on which the service is configured.

w Name: Specifies the name of the service.

w IP: Specifies the IP address of the service.

w Port: Specifies the port on which the service listens.

w Protocol: Specifies the service type that determines the behavior of the service. Forexample, HTTP, TCP, UDP, and SSL.

w State: Specifies the current state of the service. For example, UP, DOWN, and OUTOF SERVICE.

w Last State Change: Specifies the time elapsed (in days, hours, minutes, and seconds)since the last change in the state of the service, that is, the duration of time forwhich the service is in the current state.

You can also view the virtual servers to which a service is bound and further monitorthe real-time status of the virtual servers.

For information on the procedure to view the status of services, do one of the following:



Viewing the Status of Service GroupsUse Command Center to monitor the real-time values of the state of a service groupmember.

You can view the following statistics:w Device Name: Specifies the name of the device on which the service group is

configured.

w Name: Specifies the name of the service group.

w IP: Specifies the IP address of the service, which is a member of the service group.

w Port: Specifies the port on which the service group member listens.


39
http://support.citrix.com/proddocs/topic/netscaler/cc-gen-command-center40-wrapper-con.htmlhttp://support.citrix.com/proddocs/topic/netscaler/cc-gen-command-center40-wrapper-con.htmlhttp://support.citrix.com/proddocs/topic/netscaler/cc-gen-command-center40-wrapper-con.htmlhttp://support.citrix.com/proddocs/topic/netscaler/cc-gen-command-center40-wrapper-con.htmlhttp://support.citrix.com/proddocs/topic/netscaler/cc-gen-command-center40-wrapper-con.html


40/220

w Protocol: Specifies the service type that determines the behavior of the servicegroup. For example, HTTP, TCP, UDP, and SSL.

w State: Specifies the effective state of the service group, which is based on the stateof the member of the service group. For example, UP, DOWN, and OUT OF SERVICE.

w Last State Change: Specifies the time elapsed (in days, hours, minutes, and seconds)since the last change in the state of the service group member, that is, the durationof time for which the service group member is in the current state. This informationis available only for service group members configured on NetScaler release 9.0 andlater.

You can view the virtual servers to which a service group is bound and further monitorthe real-time status of those virtual servers.

For information on the procedure to view the status of service groups, do one of thefollowing:



Configuring ViewsYou can add views to monitor specific entities based on entity names, device names,protocol types, states, and health. Views make it easier to monitor a large number ofentities configured across your NetScaler infrastructure. For example, you can create aview to monitor virtual servers with protocol type as AAA.

The views you create are associated with your Command Center user account.

For information on the procedure to configure views, do one of the following:



Managing the Real-Time Status of EntitiesYou can manage the virtual servers, services, and service groups configured across allyour NetScaler devices from the Command Center console. You can set a time interval

for which you want Command Center to poll the values of the entities. You can managethe states of the entities by enabling or disabling them and view the details ofcommand execution using the Audit Trail.

You can poll the latest status of the entities at any given point of time, for example,after you have made a configuration change. You can also conduct a search for theentities based on different parameters, such as health, name, state and Type(CSVserver and LB).


40
http://support.citrix.com/proddocs/topic/netscaler/cc-gen-command-center40-wrapper-con.htmlhttp://support.citrix.com/proddocs/topic/netscaler/cc-gen-command-center40-wrapper-con.htmlhttp://support.citrix.com/proddocs/topic/netscaler/cc-gen-command-center40-wrapper-con.htmlhttp://support.citrix.com/proddocs/topic/netscaler/cc-gen-command-center40-wrapper-con.htmlhttp://support.citrix.com/proddocs/topic/netscaler/cc-gen-command-center40-wrapper-con.html


41/220

Configuring the Polling Interval

You can set the time interval for which you want Command Center to poll the real-timevalues of the virtual servers, services, and service groups. By default, Command Centerpolls the values every 300 seconds (5 minutes).

Setting the polling interval on any one of the entity nodes (Virtual Servers, Services, orService Groups) sets it across all the entity nodes.

Enabling or Disabling Virtual ServersYou can also change the state of a virtual server by enabling or disabling it.

When you enable avirtual server with a state of DOWN or OUT OF SERVICE,its statechanges to either UP or DOWN, depending on whether the actual server is UP or DOWN.If the state of the virtual server does not change to UP, log on to the NetScaler toidentify the cause and make appropriate changes to the virtual server configuration.

When you disable a virtual server with a state of UP, its state changes to OUT OF SERVICE.

For information on the procedure to configure this, do one of the following:



Enabling or Disabling ServicesYou can also change the state of a service by enabling or disabling it.

When you enable aservice with a state of DOWN or OUT OF SERVICE, its state changesto either UP or DOWN, depending on whether the actual backend server is UP orDOWN. If the state of the service does not change to UP, log on to the NetScaler toidentify the cause and make appropriate changes to the service configuration.

When you disable a service with a state of UP, its state changes to OUT OF SERVICE.



w See Command Center documentation at: http://support.citrix.com/proddocs/topic/

netscaler/cc-gen-command-center40-wrapper-con.html

Enabling or Disabling Service GroupsYou can also change the state of a service group by enabling or disabling it.

When you enable a service group member with a state of DOWN or OUT OF SERVICE,the state of the service group to which it belongs changes to either UP or DOWN,depending on whether the actual backend server is UP or DOWN. If the state of the


41
http://support.citrix.com/proddocs/topic/netscaler/cc-gen-command-center40-wrapper-con.htmlhttp://support.citrix.com/proddocs/topic/netscaler/cc-gen-command-center40-wrapper-con.htmlhttp://support.citrix.com/proddocs/topic/netscaler/cc-gen-command-center40-wrapper-con.htmlhttp://support.citrix.com/proddocs/topic/netscaler/cc-gen-command-center40-wrapper-con.htmlhttp://support.citrix.com/proddocs/topic/netscaler/cc-gen-command-center40-wrapper-con.htmlhttp://support.citrix.com/proddocs/topic/netscaler/cc-gen-command-center40-wrapper-con.htmlhttp://support.citrix.com/proddocs/topic/netscaler/cc-gen-command-center40-wrapper-con.htmlhttp://support.citrix.com/proddocs/topic/netscaler/cc-gen-command-center40-wrapper-con.html


42/220

service group does not change to UP, log on to the NetScaler to identify the cause andmake appropriate changes to the configuration of the service group.

When you disable a service group member with a state of UP, the state of the servicegroup to which it belongs changes to OUT OF SERVICE.




Viewing the Audit TrailYou can view the audit trail to identify enabled and disabled operations on virtualservers, services, and service group members.

Under Audit Trail, you can view the following:

w Settings: Opens the Settings box for specifying how often you want Command Centerto update the audit trail in seconds. By default, the refresh interval is set to 10seconds.

w Refresh: Refreshes the audit trail at the current time.

w Device: Specifies the IP address of the device on which the operation is performed.

w Operation: Specifies the operation performed on the virtual server, service, orservice group member.

w Name: Specifies the name of the virtual server, service, or service group member on

which you have performed the operation.

w Executed By: Specifies the username of the NetScaler user who performed theoperation.

w Time: Specifies the time when the operation was performed.

w Status: Specifies the status of the operation performed, which can be Success orFailed.

w Annotation: Specifies the message describing the reason why the enable or disableoperation was performed. This message was entered when performing the operation.


42
http://support.citrix.com/proddocs/topic/netscaler/cc-gen-command-center40-wrapper-con.htmlhttp://support.citrix.com/proddocs/topic/netscaler/cc-gen-command-center40-wrapper-con.html


43/220

Chapter 6

Using Tasks to Configure ManagedDevices

Topics:

Managing Built-in Tasks

Configuring Custom Tasks

Customizing Built-in andCustom Tasks

Viewing the Execution Log

for all Tasks

You can simplify device management and minimizeconfiguration errors by using built-in and custom tasks tomake configuration changes across devices, upgradefirmware, and replicate a device's configuration to otherdevices on your network.

To make configuration changes on NetScaler and Repeatermanaged devices, Command Center uses the NetScaler andRepeater command-line interface (CLI) and the Secure Shell(SSH) and Secure File Transfer Protocol (SFTP) protocols. Toview the status of the tasks executed, see the execution logthat Command Center provides.

43


44/220


45/220

w ConfigureCompression Policy: Configure compression policies on NetScaler devices.

w InstallSSLCert: Upload and install SSL certificates from the Command Center serverto the discovered NetScaler devices.

w ConfigureFilterPolicy: Configure filter policies on NetScaler devices.

Upgrading Repeater with Built-in TasksThe built-in upgrade task that you can execute on a Repeater device is:

w Software Upgrade: Use this task to upgrade one or more Repeater devices to anewer release of the Repeater software by specifying the path to the installationfile of the software version to which you want to upgrade.

Configuring Repeater with Built-in TasksThe built-in configuration tasks that you can execute on Repeater devices are:

w EnableRepeater: Enable traffic through Repeater devices.

w DisableRepeater: Disable traffic through Repeater devices.

w Add Service Class: Add a new service class and rule with details, such as serviceclass name, enable or disable acceleration, choice of compression (disk, memory, ornone), and ports.

w Configure Alert: Configure an alert (alert name and level) on Repeater devices.

w Configure Sys Log Server: Configure a new system log server for Repeater devices.

w Add User: Set up a new user account on selected devices and assign privileges.

w Configure Bandwidth: Configure the bandwidth parameters of Repeater devices.

w RestoreConfig: Restore the configuration on a Repeater device from anyconfiguration file.

w ConfigureRemoteLicenseServer: Configure multiple Branch Repeater VPX devicesto use a centralized licensing server. You can configure parameters, such as IPaddress, port of the licensing server, and the license model.

w ConfigureLocalLicenseServer: Configure multiple Branch Repeater VPX devices touse local licensing server.

w RestartRepeater: Restart the Repeater devices.

Executing Built-in TasksYou can execute a built-in task on multiple devices at the same time. You can eitherselect devices individually or select a device list for the tasks. You can execute thesame task several times on different devices or device lists. You can also preview a task(the commands and rollback commands) before executing it.

For information on the steps to execute built-in tasks, do one of the following:


45


46/220


47/220

Note: The location of the exported file is CC_Home\provisioningtemplates

\exportedtemplates.

Documents

Command Center User Guide 4 1