Dec. 18, 2015
After the devices are discovered, on the Citrix Network tab you can perform various operations specific to single devices or multiple devices.
This topic includes the following details:
The general properties of a device are:
To view Monitoring, under Device Properties, click More. The Monitoring section displays the status of monitoring parameters and status polling options:
Use Command Center to view the details of the archived files in the database as well as configuration files for the current time. Under Archived Details, view the following details:
Command Center correlates the history of events to form alarms for different severity levels and displays the events as messages, some of which may require immediate attention. For more information, see Fault.
From the Citrix Network tab, you can view the events and alarms for single devices.
You can simplify device management and minimize configuration errors by using built-in and custom tasks to make configuration changes across devices, upgrade firmware, and replicate a device's configuration to other devices on your network.
You can execute tasks on single or multiple devices on the Citrix Network tab.
You can launch the Web user interface for a selected CloudBridge device by using Command Center.
|Character||Definition /Usage||Pattern||Sample Matches|
|*||Use when you want to match zero or more characters of the keyword.||
Module - Device InventorySearch criterion - Type
Search keyword - stand*
All the devices whose state is STANDALONE
|!||Use when you want to exclude the characters of the keyword.||
Module - Device Inventory
Search criterion - Type
Search keyword - !stand
All devices whose state is not STANDALONE
|,||Use as a separator between multiple values for a filter criterion.||
Module - Device Inventory
Search criterion - Name
Search keyword - 10*,*56
All devices whose Name starts with '10' or ends with '56'.
Sample matches : 10.234.123.56 and 184.108.40.206
You may want to set a device(s) for rediscovery when you need to view the latest state of the device and its configuration file. Or, you may want to set a device for rediscovery if the device has moved to the Inaccessible Systems node.
During rediscovery, the Command Center server fetches the configuration and license files of the device, and archives them in its file system. By default, Command Center schedules devices for rediscovery once every hour. You can configure the rediscovery interval according to your preference. For instructions on how to set the rediscovery interval, see Configuring the Discovery Settings.
Using Command Center you can de-provision the NetScaler VPX instances that are provisioned on NetScaler SDX Platform.
Command Center supports devices configured in high availability mode where the primary device processes the traffic and the secondary device monitors the primary and takes over the functions of the primary device if that device is unable to continue processing traffic. You can perform a set of operations specific to the HA devices, such as forcing a failover and forcing a secondary to stay as a secondary, described in the following two sections.
Failover: When two devices are operating as an HA pair, one device is configured as the primary device and the other is configured as the secondary device. The secondary device sends periodic hello messages to the primary device to check whether it is operating. If the primary does not reply, the secondary device retries the connection with the primary for a specified time period. If the secondary device fails to re-establish communication, it determines that the primary system is not functioning as expected, and takes over as the new primary device. This process is known as failover
After a failover, all client connections must be re-established; however, the session persistence rules set before the failover are maintained after a failover.
The failover starts on the HA pair. If the force failover is successful, a confirmation message appears.
You can now configure and manage NetScaler clusters from Command Center console. You can configure a cluster from the scratch or add a configured cluster to Command Center and then, start managing the NetScaler cluster from Command Center console. The NetScaler Cluster is represented as NS CL and the device type of a cluster node is represented as 'Cluster Node' in the Citrix Network page.
A NetScaler cluster is a group of NetScaler devices working together as a single device. Each device of the cluster is called a node. A NetScaler cluster can include as few as two or as many as 32 NetScaler nCore hardware or virtual appliances as nodes. The traffic is distributed among the cluster nodes to provide high availability, high throughput, and scalability.
If you want to stop managing and monitoring a NetScaler cluster, you can delete it from Command Center. Deleting a NetScaler cluster does not change the cluster configuration but only removes the device and its related details from the database of the Command Center server. To delete a device from Command Center, see Deleting Devices