xms_v1_2_adminguide_07160c

Crossbeam X-Series Management System(XMS) Administration Guide

Version #: XMSV1.2

Part Number: 007160C

June 2013

Copyright and Trademark Information

Copyright 2013 by Crossbeam Systems

Boxborough, MA, USA

All Rights Reserved

The products, specifications, and other technical information regarding the products contained in thisdocument are subject to change without notice. All information in this document is believed to be accurateand reliable, but is presented without warranty of any kind, expressed or implied, and users must take fullresponsibility for their application of any products specified in this document. Crossbeam Systemsdisclaims responsibility for errors that may appear in this document, and it reserves the right, in its solediscretion and without notice, to make substitutions and modifications in the products and practicesdescribed in this document.

This material is protected by the copyright and trade secret laws of the United States and other countries. Itmay not be reproduced, distributed, or altered in any fashion by any entity (either internal or external toCrossbeam Systems), except in accordance with applicable agreements, contracts, or licensing, withoutthe express written consent of Crossbeam Systems.

For permission to reproduce or distribute please contact your Crossbeam Systems account executive.

This product includes software developed by the Apache Software Foundation: www.apache.org.

Crossbeam, Crossbeam Systems, X-Series, XOS, X20, X30, X45, X50, X60, X80, X80-S and any logosassociated therewith are trademarks or registered trademarks of Crossbeam Systems, Inc. in the U.S.Patent and Trademark Office, and several international jurisdictions.

All other product names mentioned in this document may be trademarks or registered trademarks of theirrespective companies.

The Crossbeam X-Series Management System makes use of the Silk Icons in the user interface. Theseicons are made available through the Creative Commons Attribution 3.0 Licensewww.famfamfam.com/lab/icons/silk/

2

ContentsCrossbeam X-Series Management System (XMS) Administration Guide 1About This Guide 4

Intended Audience 4Related Documentation 4

Chapter 1: Crossbeam X-SeriesManagement System - XMS 5XMSArchitecture 5XMS System Requirements 5

XMSServer 5Installation Notes 5XMSInstaller 6XMSClient 6

X-SeriesPlatform Requirements 7Supported XOSVersions 7

Chapter 2: Installing XMS 8Installation 8

Stopping XMS 9Configuring the XMS Server to Start on Host Reboot 9

Starting an XMS Client Session 10XMSUser Interface 11XOSSupport 12

Backup and Restore 12Backup 12Restore 13

Upgrading XMS 14Uninstalling XMS 15

Chapter 3: Licensing XMS 17Purchase a License 17

Increase the Maximum Limit 17Moving the XMS Server 17

Chapter 4: Troubleshooting 18Log Files 18Hostname Resolution 18IPTables Port Blocking 18Contacting Crossbeam Customer Support 19

3

About This Guide

About This Guide

This guide provides information for installing, configuring, and troubleshooting the X-Series ManagementSystem.

IMPORTANT: For the latest updates and revisions to X-Series Platform documentation, log into theCrossbeam Customer Support Portal at http://www.crossbeam.com/support/online-support/.

Intended AudienceThis guide is intended for administrative personnel responsible for installing, configuring, and managingthe Crossbeam X-Series Management System (XMS)software.

Related DocumentationThe following documents are provided on the Crossbeam Systems USB Installer (USBI) or are availableon the Crossbeam Systems Customer Support Portal located at http://www.crossbeam.com/support/online-support/.

l XMS Release Notes

l APM, CPM, and NPM Installation Notice

l X80-S Platform Hardware Installation Guide

l X60 Platform Hardware Installation Guide

l X20, X30, and X50 Platform Hardware Installation Guide

l XOS Command Reference Guide

l XOSConfiguration Guide

l Multi-Application Serialization Configuration Guide

l Multi-System High Availability Configuration Guide

l Install Server User Guide

l USB Installer User Guide

l RSW Installation Guide (available with the RSW kit, purchased separately)

l XOS Release Notes

4

Chapter 1:Crossbeam X-SeriesManagement System - XMS

The Crossbeam X-Series Management System (XMS) provides a graphical user interface to view thehealth and status of the X-Series Platforms on your network. XMS supports up to 100 X-Series Platformsand 10 client sessions on each XMSserver.

Crossbeam customers can download XMS as a 30-day trial from the Crossbeam Download portal.

XMSArchitectureThe Crossbeam X-Series Management System is a database application installed on a dedicated server.XMSuses a browser-based interface to provide at-a-glance status of all the X-Series Platforms on yournetwork.

After installing XMS, the administrator opens a secure browser connection to the XMSserver and adds theX-SeriesPlatforms to be monitored.

Users log in to the server through an HTTPS connection on their local machine. The XMSinterfacedisplays the current X-Series Platform status, hardware and software details, and a record of alarms andevents for each system. Functions within XMS such as importing devices and applying licenses are basedon user privilege levels; Administrator, Operator, or Viewer.

For more information about using XMS, refer to the XMSOnline Help after installation.

XMS System RequirementsThe XMSServer, Installer, and Client have the following requirements.

XMSServerThe XMSServer has the following system requirements:

l 1 GB free disk space

l 1 GB RAM

l 1 GHz CPU

l Red Hat Enterprise Linux v6 (RHEL6) or CentOS6

l 64-bit architecture on the following processors: AMD64, EM64T, and x86-64

Installation NotesPrior to installation, verify that the XMSServer hostname appears in both DNS and the /etc/hosts file.

If you are installing on a VMWare image, XMSis supported on VMWare Version ESXi 4.1. The VMWarevirtual machine must be installed prior to installing XMS.

Verify that the iptables firewall configuration is not blocking port 8443. By default, iptables blocks port8443, which will prevent connection to XMS.

5

1

Chapter 1: Crossbeam X-SeriesManagement System - XMS

XMSInstallerThe following components are required by the XMSInstaller to perform the installation. They are not usedby the XMS application.

l Unzip

l JRE 1.4 or higher. Supported JVM's include:

l Sun 1.4.x, 1.5.x, 1.6.x

l IBM 1.4.x, 1.5.x, 1.6.x

l Apple 1.4.x, 1.5.x, 1.6.x

l HP 1.4.x, 1.5.x, 1.6.x

XMSClientThe XMS Client has the following system requirements.

l 2 GHz, dual-core processor, with 2GB RAM

l 4 GBRAMis recommended for optimal performance when running 20 or more devices

l Minimum screen resolution of 1024 x 768

Fully Supported Operating Systems and Browsers

NOTE: Crossbeam recommends Google Chrome or Mozilla Firefox for the best user experience.

l Microsoft Windows 7 or XP

l Google Chrome

l Firefox

l Internet Explorer 9 on Windows 7

l CentOS 6

l Google Chrome

l Firefox

l OSX 10.5

l Google Chrome

l Firefox

l Safari 5

6

Chapter 1: Crossbeam X-SeriesManagement System - XMS

Limited Support Operating Systems and Browsers

l Internet Explorer 8 on Windows XP

Due to performance limitations in IE8, only 20 devices are supported with 4GB RAM, and up to 50devices are supported with 8GB RAM. Access is also limited to day-to-day operations (rather thanprojecting the display for an extended period of time). If support for more than 50 devices is required,or use for longer than day-to-day operations, or if you experience slow performance, Crossbeamsuggests using one of the recommended Web browsers.

X-SeriesPlatform RequirementsXMShas the following requirements for each X-Series Platform to be monitored.

Supported XOSVersionsXMS supports the following versions of XOS:

l XOS V9.7.x

l XOSV9.6.x

l XOSV9.5.x

l XOSV9.0.x - Support is limited. See XOSV9.0.x Support for more information.

SNMPSettingsIn order for the XMSServer to communicate with the X-Series Platform, SNMP must be configured on thechassis. Refer to the XOSCommand Reference Guide for a detailed explanation of the commands toconfigure SNMP.

7

Chapter 2:Installing XMSThis section describes the XMS installation process. Be sure to read the XMSRelease Notes beforebeginning the installation, as they contain the latest information relating to the installation, set up, and useof XMS.

If you currently have XMS installed , please see Upgrading XMS on page14 for the upgrade procedure.

InstallationUse the following process to install XMS on a server.

1. Download the XMS installation package from the Crossbeam download site to the server that willhost the XMSapplication.

NOTE: Some download processes change the read/write/execute permissions of the installprogram. You may be required to reset the permissions of the file to execute theinstallation. From the command line, run chmod +x XMS-Install-1.2.x-y.

2. Launch the installer utility. The install process can be run as an install wizard from the GUI, or itcan be run from the command line. Installing XMSas a non-root user is the recommendedapproach. The non-root user installation restricts the permission level of the application, andprevents potential security vulnerabilities.

l From the linux directory use ./XMS-Install-1.2.x-y (run in GUI mode)

l To force the installer to run on the CLI, use ./XMS-Install-1.2.x-y -iconsole

3. The XMS Install wizard verifies that your system has sufficient disk space for the application. Ifthere is not enough disk space, the XMS installer displays the following message:

Not Enough Disk Space---------------------Warning!This installation requires 1 GB of free disk space, but there are only MB available at:~jdoe/cbs/XMS-1.2.x.y

Please free at least MB to proceed with the installation.PRESS TO RECALCULATE AVAILABLE DISK SPACE,OR TYPE 'QUIT' TO EXIT THE INSTALLER:

4. XMSautomatically provides a 30-day evaluation license. You must accept the license agreementto continue.

5. The application is installed by default into the user's home directory. For example, if the user werejdoe, the application would be installed in: ~jdoe/cbs/XMS-1.2.x.y

6. Click Next to complete the installation.

7. After the XMSinstallation completes, Crossbeam recommends changing the password of thedefault admin account. The default login is admin / admin, which if left unchanged poses asecurity risk. Use the password reset script located in the installation directory.

~jdoe/cbs/XMS-1.2.x.y/util/resetpassword.sh

8

2

Chapter 2: Installing XMS

The following requirements are enforced when a user creates a password for XMS.

l Minimum length of 8 characters

l Maximum length of 32 characters

l At least 1 upper-case letter

l At least 1 lower-case letter

l At least 1 digit

l At least 1 special character: !, @, #, $, %, ^, &, *, (, or )

8. Start the XMS server from the command line using the following command:

cd ./StartXMS.sh

For example:cd ~jdoe/cbs/XMS-xxx./StartXMS.sh

Any time the server hosting XMS reboots or is restarted,XMSmust be restarted. You can configure theXMSServer to restart automatically, or use the above command to restart XMS manually. See Configuringthe XMS Server to Start on Host Reboot on page9 for more information.

Stopping XMSIf you need to shut down the XMSserver for any reason, use the following command to do so safely.

NOTE: To backup the XMSdatabase, refer to Backup and Restore on page12.

Use the StopXMS.sh script in the install directory to shut down the XMSserver.

cd ./StopXMS.sh

For example:

cd ~jdoe/cbs/XMS-1.2.x.y./StopXMS.sh

Configuring the XMS Server to Start on Host RebootThe XMSserver can be configured to start automatically on a host reboot. Use the following steps toconfigure this option.

If XMSwas installed as a non-root userInstalling XMSas a non-root user is the recommended approach. The non-root user installation restrictsthe permission level of the application, and prevents potential security vulnerabilities. For this example,assume that the administrator's username is xmsadmin:

1. From the Linux CLI, switch to root.

2. Add the following line to the end of /etc/rc.local:

su xmsadmin /home/xmsadmin/cbs/XMS-1.2.x.y/StartXMS.sh

9


If XMSwas installed from root:

1. From the Linux CLI, switch to root.

2. Add the following line to the end of /etc/rc.local:

/root/cbs/XMS-1.2.x.y/StartXMS.sh

Starting an XMS Client SessionYou can open an XMS client session from any machine that can access your XMSserver.

1. Open your browser and establish a secure http connection to the XMSserver.

https://:8443/xms

or

https://:8443/

2. Change the default username and password for XMS, if you have not done so already.The default user name and password for XMS is admin/admin. If the default password was notchanged after the installation completed, Crossbeam strongly recommends changing it the firsttime you log in to the XMSserver from a client session. The password can be changed from theSettings window. Click Settings in the title bar to open the window.

The following are the password requirements for XMS.

l Minimum length of 8 characters

l Maximum length of 32 characters

l At least 1 upper-case letter

l At least 1 lower-case letter

l At least 1 digit

l At least 1 special character: !, @, #, $, %, ^, &, *, (, or )

3. XMSopens to the Device List Tab. Add individual devices to the view using the New Devicebutton.

Adding Multiple Devices To XMSYou can automatically import multiple devices into XMSusing a comma separated value (CSV) text file.The Import Devices function reads the file and imports the devices into XMS.

A CSV file is a simple text file containing a list of entries, where each line represents a device. Each line ispopulated with values including IP address, device name, and SNMP data, separated by commas. TheSNMP information required is dependent on the version of SNMP being used.

To add multiple devices to XMS, click the Import button on the Device List Tab. For details about using aCSV text file to import devices into XMS, refer to the online help for the Import Devices dialog.

10


XMSUser InterfaceUse the tabbed interface to gather information about the X-Series Platforms operating on your network. Formore information, refer to the individual online help topics for each tab.

Device List

l The Device list shows the machine name and current information for each configured X-SeriesPlatform, and allows you to add new devices one at a time, or to import multiple devices using aCSV file.

Status Map Tab

l The Status Map tab shows a graphic representation of each system, including machine name,model, and IP address. This view contains all devices in a single screen, providing an at-a-glanceview of the status of your entire Crossbeam network. This makes it easy to monitor the overallhealth of the entire Crossbeam network and to detect status changes on any device.

Inventory Tab

l The Inventory tab displays a list of all the Crossbeam devices on the network and the modulesinstalled in each chassis. This view allows adminstrators to review the currency of individualcomponents and to generate reports of the equipment inventory in CSV format.

DBHATab

l The DBHA tab displays a list of systems connected in high availability groupings. This viewmonitors the health of DBHA in your network, providing you with assurance that the network isoperating properly and backup systems are ready to takeover if needed.

Event Log

l The Event Log displays a log of all events on each system, including XOS alarms occurring on thechassis as well as audit events occurring on the XMS Server.

Settings Window

l The Settings window provides access to user management functions for users and administrators,based on the privilege level assigned by the system administrator.

11


XOSSupportXMS supports devices running XOS V9.7.x, V9.6.x, V9.5.x, and V9.0.x. Devices running XOS V9.0.x use aprevious version of the Crossbeam MIB that provides less status information, limiting some features withinXMS for those devices.

XOSV9.0.x SupportThe information displayed for an X-Series Platform running XOS V9.0.x is limited in the following ways:

l Alarm counts are not available. The Device List > Alarm Summary indicates the severity of thehighest active alarm.

l Application data is not available. The Device List > Application field displays Unavailable.

l Uptime is not available. The Device List > Uptime field displays Unavailable.

l Part numbers for the chassis and components are not available. The Inventory > Part Numberfield is blank.

l Active alarm data is not available. The Event Log does not display alarm information for V9.0.xdevices.

l DBHAconfiguration information is not available.

Backup and RestoreXMSprovides scripts that allow you to backup the XMSdatabase, and to restore the database from thebackup file. The backup.sh and restore.sh scripts are located in the /util sub-directory within theXMS deployment. For example, if the user were jdoe, the scripts would be located in:

~jdoe/cbs/XMS-1.2.x.y/util/backup.sh~jdoe/cbs/XMS-1.2.x.y/util/restore.sh

If the XMS server is running at the time the backup or restore script is executed, the script will prompt theuser to shut down the server for the duration of the operation. The script automatically restarts theXMSserver after the operation has completed. See Stopping XMS on page9 for information on shuttingdown XMS.

BackupUse the following command from the install directory to perform an XMSdatabase backup:

cd /util./backup.sh -f backup1

If executed without any arguments, the script auto-generates the filename for the database file. Thearguments available for use with the backup command are:

l -h: Displays the usage of the backup script.

l -s: Shuts down the XMS server without prompting the user. The default behavior is to prompt theuser before shutting down, if XMS is running.

l -f : Create a backup file using the filename provided. The default behavior is to auto-generate the file along with a date and time stamp.

Use the following procedure to back up the XMSdatabase.

12


ProcedureUse the following procedure to manually shut down the server before performing the backup. If you shutthe server down manually, the backup script will not automatically restart the server. It must be restartedmanually.

1. Shut down the XMSServer. Use the StopXMS.sh script in the install directory.

cd ./StopXMS.sh

For example:


2. Back up the XMSdatabase.

cd /util./backup.sh -f backup1

3. Restart the XMSServer. Use the StartXMS.sh script in the install directory.

cd ./StartXMS.sh

RestoreUse the following command from the install directory to perform an XMSdatabase restore:

cd /util./restore.sh -f backup1

When you execute the restore script, you must provide the filename of the backup file using the -fargument. The arguments available for use with the restore command are:

l -h: Displays the usage of the restore script.

l -s: Shuts down the XMS server without prompting the user. The default behavior is to prompt theuser before shutting down, if XMS is running.

l -f : Restore using the contents of the file with the provided filename.

Use the following procedure to restore the XMS server database from the contents of the specified file.

If the XMS server is running at the time the backup or restore script is executed, the script will prompt theuser to shut down the server for the duration of the operation. The script automatically restarts theXMSserver after the operation has completed. See Stopping XMS on page9 for information on shuttingdown XMS.

13


ProcedureUse the following procedure to manually shut down the server before performing the restore. If you shutthe server down manually, the restore script will not automatically restart the server. It must be restartedmanually.


cd ./StopXMS.sh

For example:


2. Restore the XMSdatabase.

cd /util./restore.sh -f backup1

3. Restart the XMSServer. Use the StartXMS.sh script in the install directory.

cd ./StartXMS.sh

Upgrading XMSThe XMSupgrade process automatically migrates your existing XMSdatabase into the latest version of theapplication. Be sure to read the XMSRelease Notes before beginning the upgrade, as they contain thelatest information relating to the upgrade, set up, and use of XMS. Use the following process to upgradeXMS.

NOTE: The upgrade command should be run by the same user who installed XMS. The originalinstallation was placed in the user's home directory. When an upgrade is performed by a differentuser, the location of the original installation may not be accessible, and the upgrade may fail.

1. Download the XMS Upgrade package from the Crossbeam download site to the server that hoststhe XMSapplication.

NOTE: Some download processes change the read/write/execute permissions of the upgradeprogram. You may be required to reset the permissions of the file to execute theupgrade. From the command line, run chmod +x XMS-Upgrade-1.2.x-y.

2. Launch the upgrade utility. The upgrade process can be run as a wizard from the GUI, or it can berun from the command line.

l From the linux directory use ./XMS-Upgrade-1.2.x-y (run in GUI mode)

l To force the upgrade to run on the CLI, use ./XMS-Upgrade-1.2.x-y -iconsole

14


3. The XMS Upgrade wizard verifies that your system has sufficient disk space for the application. Ifthere is not enough disk space, XMS displays the following message:

Not Enough Disk Space---------------------Warning!This installation requires 1 GB of free disk space, but there are only MB available at:~jdoe/cbs/XMS-1.2.x.y

Please free at least MB to proceed with the installation.PRESS TO RECALCULATE AVAILABLE DISK SPACE,OR TYPE 'QUIT' TO EXIT THE INSTALLER:

4. The upgraded application will be located in the same deployment directory as the previousversion. For example, if the previous version is located in ~jdoe/cbs/XMS-1.0.a.b, then theupgraded version will be located in ~jdoe/cbs/XMS-1.2.x.y. The previous version will be left ondisk; it will not be removed automatically.

5. Click Next to complete the upgrade operation.

6. Click on the Start XMS checkbox to launch XMS automatically when the upgrade is complete.

If the upgrade process encounters any errors, a message will be displayed notifying you of the issue. Theupgrade will automatically restore your previous XMS application as it was prior to the upgrade.

Uninstalling XMSIn the event that you need to uninstall XMSfrom your system, use the XMSUninstall utility. Prior touninstalling XMS, you should run the backup command on the server to save the database.

The uninstallation can be run from the GUI or from the command line. The uninstaller is located in thedirectory where XMSwas installed and by default will run in the mode in which the application wasinstalled (GUI or CLI). You can force the installer to run in either console or GUImode by using theappropriate command.


cd ./StopXMS.sh

For example:

cd ~jdoe/cbs/XMS-1.x.y.z./StopXMS.sh

2. Back up the XMSdatabase to a location different than the Install directory. This prevents thebackup file from being deleted during the uninstall.

cd /util/./backup.sh -f ~/backup1

15


3. Uninstall XMS.

l To run the uninstallation in the same mode as the installation, use the followingcommand run from the install directory: ./XMS-Uninstall.bin

cd ./XMS-Uninstall.bin

l To force the uninstall to run on the CLI, use XMS-Uninstall.bin -i consolefrom the CLI.

cd ./XMS-Uninstall.bin -i console

l To force the uninstall to run in GUImode , use XMS-Uninstall.bin -i gui fromthe CLI.

cd ./XMS-Uninstall.bin -i gui

16

Chapter 3:Licensing XMSThe XMS download is a full featured version that allows you to manage an unlimited number of X-SeriesPlatforms for free, for 30 days. To continue using XMSbeyond the 30-day evaluation period, you mustpurchase an XMS license.

Purchase a LicenseTo purchase a license, please provide Crossbeam or your Crossbeam partner with the followinginformation:

l The XMS server fingerprint. The fingerprint information is available in the License tab of theSettings dialog box, in the XMS user interface. For more information, refer to the XMS online help.

l The maximum number of X-Series Platforms to be managed by the XMS server. Once the XMSlicense has been applied to the XMS server, the maximum limit on the number of devices isenforced. If you expect to be monitoring additional X-Series Platforms in the future, be sure tochoose the maximum device number accordingly. If your network grows beyond the limit of yourcurrent license, you can purchase a new license for an increased limit.

After receiving the license from Crossbeam, use the License tab in the Settings dialog box to apply thelicense key to XMS. Licenses are perpetual, and will be retained during an XMSupgrade. If you needadditional information, please refer to the XMSOnline Help.

Increase the Maximum LimitTo manage additional devices beyond the current limit, you must purchase a new XMS license. Pleaseprovide Crossbeam or your Crossbeam partner with the following information:

l The XMS server fingerprint.

l The number of X-Series Platforms you would like to add to your current license.

Crossbeam will generate a new license key, indicating support for the *total* number of devices (currentmaximum, plus the new devices), and send you the new license key. Apply this license key in place of theoriginal key, in the License tab in the XMS user interface.

Moving the XMS ServerMoving the XMS Server to a new machine is supported.

1. Use the backup script on your XMSServer to backup your current database.

2. Follow the Installing XMS instructions to install a new, trial version of XMS on the new server.

3. Use the restore script on the new server to load the original database into the new XMSServer.See Backup and Restore on page12 for more information.

4. After the installation and configuration is complete, use the Unlicense button on the License Tabof the Settings dialog to remove your license from the old XMSserver.

5. Contact Crossbeam or your Crossbeam partner with the new server fingerprint information andyour existing license information. Crossbeam will provide a new license key that will manage thesame number of devices as the previous license.

17

3

Chapter 4:TroubleshootingUse the following information when troubleshooting the XMSinstallation and production use.

Log FilesThere are two log files where XMSinformation is stored.

l The XMSlog file is the engineering log file for the XMS application. It contains log messagesgenerated by various software components within XMS. The xms.log file is located in /log/.

l The apache tomcat log file contains useful troubleshooting information, however it is notspecifically generated by XMS. The file name is catalina.out, and is located in /apache-tomcat-x.y.z/logs/.

Hostname ResolutionIf you see the following error during installation, the hostname has not resolved to an IPaddress. Verifythat the XMSServer hostname appears in both DNS and the /etc/hosts file.

Example:Hostname resolution-------------------The hostname of the server does not resolve to an IP address. This mighthinder XMS from contacting devices on the network. Please ensure that thehostname resolves to an IP address.PRESS TO CONTINUE:

Solution:Verify the hostname and add it to both the DNS and /etc/hosts file.

[root@ironman admin]# hostnameironman.crossbeam.com

127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4ironman ironman.crossbeam.com

If you add a device before verifying or adding the XMSserver's hostname, the device will show NeverContacted in the XMS interface.

IPTables Port BlockingVerify that the iptables firewall configuration is not blocking port 8443. By default, iptables blocks port8443, which will prevent connection to XMS.

18

4

Chapter 4: Troubleshooting

Contacting Crossbeam Customer SupportWhen contacting Crossbeam Customer Support, be sure to have your XMSserver fingerprint,XMSLicense key, and XOSinformation on hand.

Crossbeam Systems offers a variety of service plans designed to meet your specific technical supportrequirements. For information on purchasing a service plan for your organization, please contact youraccount representative or see http://www.crossbeam.com/support/technical-support/.

If you have purchased a Crossbeam Systems product service plan and need technical assistance, you canreport issues by telephone:

United States:+1 800-331-1338 OR +1 978-318-7595

EMEA:+ 33 4 8986 0400

Asia Pacific:+1 978-318-7595

Latin America:+1 978-318-7595

You can also report issues via e-mail to [email protected].

In addition, all of our service plans include access to the Crossbeam Customer Support Portal located athttp://www.crossbeam.com/support/online-support/.

The Crossbeam Customer Support Portal site provides you with access to a variety of resources, includingCustomer Support Knowledgebase articles, technical bulletins, product documentation, and release notes.You can also access our real-time problem reporting application, which lets you submit new technicalsupport requests and view all your open requests.

Crossbeam Systems also offers extensive customer training on all of its products. For current courseofferings and schedules, please refer to the Crossbeam Education Services Web pages located athttp://www.crossbeam.com/support/training-services/.

19

Crossbeam X-Series Management System (XMS) Administration GuideAbout This GuideIntended AudienceRelated Documentation

Chapter 1: Crossbeam X-Series Management System - XMSXMS ArchitectureXMS System RequirementsXMS ServerInstallation NotesXMS InstallerXMS Client

X-Series Platform RequirementsSupported XOS Versions

Chapter 2: Installing XMSInstallationStarting an XMS Client SessionXMS User InterfaceXOS Support

Backup and RestoreBackupRestore

Upgrading XMSUninstalling XMS

Chapter 3: Licensing XMSPurchase a LicenseIncrease the Maximum LimitMoving the XMS Server

Chapter 4: TroubleshootingLog FilesHostname ResolutionIPTables Port BlockingContacting Crossbeam Customer Support

xms_v1_2_adminguide_07160c

Documents