While most installations complete smoothly, some installations require knowledge of the appliance’s internal structure or the use of little-known features before you can perform additional monitoring and troubleshooting. These troubleshooting tips provide information and techniques that allow a more in-depth analysis of the appliance.
Some reports show addresses on the private subnets within the CloudBridge 4000/5000, so it’s good to know what these addresses mean. These subnets connect the virtual machines together, without connecting to external ports.
All these addresses are on the local link subnet 169.254.0.0/16, described in RFC3927. This address space is segmented into three partly overlapping subnets: system management, private traffic, and accelerator management subnets.
|apA IP, accelerators 1-8||169.254.10.21/24 - 169.254.10.28/24|
|apA Signaling IP, accelerators 1-8||169.254.10.121/24 - 169.254.10.128/24|
|Accelerator unified management IP (controls all accelerators)||169.254.0.20/24|
|Primary Port IP, accelerators 1-8||169.254.0.21/24 - 169.254.0.28/24|
You can also log into the NetScaler instance directly from your browser if you know its IP address on the management port (port 0/1).
Once logged in, you will see the NetScaler GUI, which identifies itself as NetScaler VPX at the top of the page.
This is the standard NetScaler user interface. Using monitoring features is safe. Configuration changes should be made with caution, as the CloudBridge 4000/5000 makes undocumented assumptions about how the NetScaler instance is configured.
The ping and traceroute utilities are not available on the accelerator instances, as they are on other CloudBridge products. Instead, you can use the equivalent features on the NetScaler instance, using the Diagnostics page as shown below.
These features will work over your external network and on the appliance’s internal subnets.
The system below shows a conditions worth investigating:
For each warning or error, additional details are available through the Details links or Show Events buttons.
You can log into some of the virtual machines from the management port (port 0/1) using an ssh utility (such as PuTTY on Windows), logging in either as root or nsroot and using the administrative password. This will give you a shell prompt.
The most common use for logging on via SSH is to restore the IP address of an instance, typically the management service, that has become unreachable due to misconfigured network parameters. Otherwise, SSH is not recommended, as configuration changes can render the appliance unstable or unusable.
If neither of the two instances below are accessible over the network, you can log into the XenServer instance using the RS-232 port, which will give you a shell prompt.
|Management Service||nsroot||Admin password||root|
|Management Service||root||Admin password||root|
Once logged into one of these virtual machines, you can use SSH from the shell prompt to reach the NetScaler instance or the accelerator at the appropriate 169.254.x.x address.
The usual UNIX/Linux commands are available, including the vi text editor.
Logging into the accelerator GUI IP allows you to manage all the accelerator instances as a unit. Changes are automatically propagated to all the accelerator instances.
On rare occasions, you may wish to troubleshoot individual accelerator instances. To do this, use the following URL’s:
The login for the instances is admin. The password is the same admin password as is used on the other instances.
This is recommended for monitoring, not for making permanent changes, since any parameter you set in an instance may be overwritten later by the synchronization process.
The update bundles distributed by Citrix are in a simple .tgz format (a tar archive compressed with gzip). It is sometimes useful to extract individual components from the archive, rather than going back to the the Citrix Web site and downloading them individually. This is most commonly useful with the management service (build-svm*.tgz) or the accelerator release (orbital*.bin).
The update bundle can be managed by tar/gzip or by archiving utilities like 7-zip.