Frequently Asked Questions

casp10
Features
Q: What are the key updates to CA Spectrum 10.0?
A:
CA Spectrum® r10.0 contains the following key updates to the product:
  • Significantly Improved Scale through Spectrum 64-Bit Support - Check out the performance video on YouTube!
  • Support for Virtual Port Channel - Check out the vPC video on YouTube!
  • Support for Virtual Switching (VSS) - Check out the VSS video on YouTube!
  • GIS Map Integration - Check out the GIS view video on YouTube! 
  • Spectrum Reporting Enhancements - Check out the Generating SRM Reports video on YouTube!
  • Search Query Management - Check out the video on YouTube!
  • VMware Maintenance Mode - Check out the video on YouTube!
  • Enhanced Device Search - Check out the Search Query Management video on YouTube!
  • CA IM User Community Voted Enhancements
  • Platform Updates & Certifications
  • Other Functional Enhancements, Stability and Quality Improvements
INSTALL
Q: What Operating Systems are supported for the SpectroSERVER in 10.0?
A:
 CA Spectrum r10.0 supports the following Operating Systems:
  • Windows Server 2008 SP2 (64-bit)
  • Windows Server 2008 R2 SP1 (64-bit)
  • Windows Server 2012 (64-bit)
  • Windows Server 2012 R2 (64-bit)
  • Red Hat Enterprise Linux 5.x (64-bit)
  • Red Hat Enterprise Linux 6.x (64-bit)
  • Red Hat Enterprise Linux 7.x (64-bit)
  • X-based desktop environment (such as KDE or GNOME)
  • Solaris 10 with CDE
  • Solaris 11
  • X-based desktop environment (such as GNOME)
Q: Where can I download 10.0?
A:
CA Spectrum 10.0 is only available in the "Download Center" on the http://support.ca.com  website. When you launch into the support website, log in. Once logged in, enter "CA Spectrum" into the "Optionally tailor your experience to a specific product" section. Next, hover over the "Download Center" and select "Download Products" in the menu that opens. In the Download Products page, select one of the following product selections:
  • CA Spectrum Device Based Suite
  • CA Spectrum Device Based Suite – MULTI-PLATFORM
  • CA Spectrum Device Based Suite Server for IM/II (FOC)
Under the "Select a Release" area will be an option for 10.0. Select the 10.0 release with a "gen level" of 0 (zero) and click the Go button. From this page you can select the Spectrum and/or CABI package you need. When you click the "Download" button, you will be brought to a page where you can use the CA Download Manager or process an order for an ftp link to download the package.
If you do not see a CA Spectrum Device Based Suite selection, contact your CA Account Representative or the CA Global Support Center at 1-800-CALL-CAI
Q: Can I install and run CA Spectrum 10.0 on CentOS?
A:
Yes. You can use CentOS however CA Spectrum Support does not officially support running CA Spectrum on CentOS therefore you run this at your own risk.
Q: Is there a 32 bit version of 10.0?
A:
No, and therefore you cannot install CA Spectrum 10.0 on a 32 bit operating system.
Q: Does the MLS (main location server) still exist in Spectrum 10.0?
A:
Yes, the MLS still exists in 10.0 and functions the same in 10.0 as it has in previous versions (in 9.2, 9.3, 9.4, and 10.0 there needs to be only one main SpectroSERVER designated as the main location server. You cannot use a tiered approach and have multiple main location servers specified).
Q: Is there anything I should know about upgrading from Spectrum 9.2.x to 9.3/9.4/10.0 regarding Report Manager?
A
: The Report Manager database table engines are converted from MyISAM to InnoDB. This process can take a while and starts happening when you start Spectrum Tomcat for the first time. The tomcat log will contain details around where we are at in the process but will not give a timeline on when it will finish. The tomcat log is located in $SPECROOT/tomcat/logs (stdout.log on Windows and catalina.out on *nix).
 This DB schema conversion works only for upgrades from 9.2.x to 9.3.x and 9.4.x. You cannot perform a direct upgrade from 9.2.x to 10.0. If you wish to upgrade from 9.2.x to 10.0 you first need to upgrade to either 9.3.x or 9.4.x and then upgrade to 10.0. 
Q: Are you also updating CABI/BOXI that works with Report Manager?
A:
Yes, we are upgraded to CABI 4.1 SP3.
Q: Do I have to upgrade CABI to 4.1 SP3 if I’m already running 3.2 or 3.3 SP1?
A:
Yes, CA Spectrum 10.0 only works with CABI 4.1 SP3. If you are running 3.2 or 3.3 SP1 you must update CABI to 4.1 SP3 after installing CA Spectrum 10.0 (note there is no upgrade as stated in the next question).
Q:  Can I upgrade from CABI 3.x to CABI 4.1?
A:
 CABI 4.1 must be a fresh install on a new machine. Ideally you will obtain updated hardware or a new vm with better resources and install CABI 4.1 on it. Once the CABI 4.1 install is complete, there is a postinstall utility that ships on the CABI 4.1 SP3 cd that you will need to run on the new CABI 4.1 machine (it's called Postinstall.sh in the Postinstall directory). This will migrate your CABI data from the old 3.x CABI system to the new 4.1 CABI. If you do NOT do this, and you install over the top of CABI 3.x, you will lose all of your CABI data.
Q:  How can I install CABI 4.1 on Linux or Solaris since the install is in .iso format? 
A:
You need to mount the iso in order to install the CABI 4.1 package
Q:  Are there any other patches for CABI that are needed?
A:
 Yes, but only if you will be using the "multi-SRM" functionality. You will need to obtain and install patch 9 for CABI 4.1 SP3 at the following location:
Q:  If I'm installing on 64 bit Linux, are there any 32 bit libraries needed? 
 
A:
  Yes, even though the SpectroSERVER is 64 bit CA Spectrum still utilizes 32 bit libraries for other components. Refer to technical bulletin TEC1947907 for information on the specific 32bit and 64 bit packages that are needed.
Q:  Is 64 bit java jre client required?
A:
 Yes, to take full advantage of the performance, 64 bit java jre version is needed to utilize CA Spectrum 10.0.  If you are using a 32 bit client it may work, until more RAM is configured for the client by the Spectrum Administrator.  At which point you may not even be able to launch your client if you are still using a 32 bit client.
Q.  After installing CA Spectrum 10.0 users are not able to launch a client or log into the system because of a java error in regards JCEUnlimited Strength files.
A.  You need to utilize the JCEUnlimited Strength local_policy.jar file. Further information on the JCEUnlimited Strength files is documented in TEC616352 and TEC614052
Upgrade
Q: What upgrade paths are supported?
A:
We support upgrade/migration from 9.3.x and 9.4.x to 10.0
We started supporting multi-byte characters after 9.2.x. Therefore an update from 9.2.x involves going to 9.3 or 9.4 (for the data type conversion to happen) before going to 10.0.
For Example:
If you are running CA Spectrum 9.1.x or prior, you MUST install the base 9.2.0, then 9.2.2 (also known as H08) or any 9.2.3 hotfix and above. Then you must install 9.4.0, then install 10.0.
If you are running CA Spectrum 9.2 with any hotfix prior to 9.2.2 (ie. 9.2.1, H06 or H07) you MUST install 9.2.2 (H08) or any 9.2.3 hotfix and above. Then you must install 9.4.0, then install 10.0.
For example, if you are running 9.2.1 with Hotfix 6, then you must install hotfix h08 or above (ie. h10 or h12 or h13) then install 9.4, then install 10.0
If you are running CA Spectrum 9.2 with any hotfix including 9.2.2 (H08) or after (ie. H09, 9.2.3, H11, H12, H13), you must install 9.4.0, then install 10.0.
For example, if you are running 9.2.3 with H12, then all you need to do is install 9.4.0, then install 10.0
If you are running CA Spectrum 9.3 with no hotfixes, then you can install 10.0 without installing anything else first.
If you are running CA Spectrum 9.3 hotfix H01, H02, or H03, then you can install 10.0 without installing anything else first.
If you are running CA Spectrum 9.4, 9.4.1, 9.4.2, or 9.4.2.1 then you can install 10.0 without installing anything else first.
Keep in mind that any upgrade from 9.2.x will need to be converted to support the UTF-8 encoding so the install will take longer.
For example, if you are running any version of 9.2.x when you install 9.4, the UTF-8 conversion will take place.
You do not need to start the SpectroSERVER between installs. You can install 9.4.0, shut down the CA Spectrum processes and install 10.0. Once 10.0 is installed, then start the SpectroSERVER.
Q: Do you have more information on the UTF-8 conversion if I am running 9.2.x and I will be upgrading to 10.0?
A:
CA Spectrum Release 9.3, 9.4, and 10.0 use the UTF-8 encoding in all databases (SpectroSERVER, Archive Manager, Report Manager)
CA Spectrum deployments 9.2.x and prior use other encodings
Conversion of databases of those deployments to UTF-8 is mandatory during an upgrade or migration during the 9.3 and 9.4 installs.
During upgrade or migration, if you select to install Report Manager, it is converted to UTF-8 once the Tomcat service is started
Report Manager is unavailable until the conversion finishes
While upgrading from CA Spectrum 9.2.x, you must specify the character set encoding that your system is currently using.
The installer prompts you for this information so that it can automatically convert your SpectroSERVER, DDM, and Spectrum Report Manager databases
Take note that installation times may drastically increase if you have created custom event and alarm files due to the UTF-8 conversation. There is a process to run this conversion prior to installing 9.4. Refer to
Q: In a distributed SS (DSS) environment, what is the supported and best practice for upgrading servers?
A:
Upgrade the Primary MLS (main location server) SpectroSERVER first, followed by the Primary OneClick server, followed by the remaining Primary SpectroSERVERs. Upgrade the Secondary SpectroSERVERs last (including all SpectroSERVER and non primary OneClick servers). Once all SpectroSERVERs have been upgraded, be sure to stop and restart all CA Spectrum OneClick tomcat processes again to update the tomcat cache with the updated SS info. Not doing this will cause OneClick issues, such as landscapes not showing in the client.
Q: If I migrate to new hardware from 9.3 to 10.0, is the SSdb migration still available?
A:
Yes, you will need to move copies of your SSdb and DDMdb to the new hardware, and install CA Spectrum 10.0 on top. Refer to the Migrating your database section in the CA Spectrum Installation section.
Performance
Q: What are the OS memory requirements for SS/OC/SRM in 10.0?
A:
The minimum memory requirement for the SpectroSERVER is 8GB of RAM for an SS only install. However 8 GB of RAM is only suggested on smaller scale servers. In general, 16GB of RAM will be needed, and for the large servers that will be modeling close to 1,000,000 models, 32 GB of RAM may be needed. We expect that most SpectroSERVERs will need at least 16GB of RAM.
The minimum memory requirement for the OneClick process without Spectrum Report Manager (SRM) is 4 GB of RAM. Certain situations may call for more however in general, we expect this will be sufficient. Note that this is the process requirement and you will need more memory on the server to accommodate for this.
The minimum memory requirement for the OneClick process with SRM is 8GB of RAM. Certain situations may call for more memory, however, we expect this will generally be sufficient. Note that this is the process requirement and you will need more memory on the server to accommodate for this.
The minimum memory requirement for the OneClick process client is 1 GB of RAM. However in testing we found that OneClick clients connecting to SpectroSERVERs that were heavily utilized (ie. near 1 million models and/or lots of GC) needed 2GB of RAM. Note that this is the process requirement and you will need more memory on the server to accommodate for this.
Your swap/virtual memory will depend upon the OS version and the physical memory (RAM) installed. For detailed information on swap space see Swap Space Recommendations.
Swap Space Recommendations
Windows 
        
Amount of Installed RAM
Recommended swap space
    
16- 32 GB
   16 GB
Solaris
System Type
Swap Volume Size
Dump Volume Size
Mid-range server with about 8 GB of physical memory
2 GB
4 GB
High-end server with about 16 to 128 GB of physical memory
4 GB
8-64 GB
Red Hat Enterprise Linux 5
Amount of installed RAM
Recommended swap space
4GB - 16GB
4GB swap space
16GB - 64GB
8GB swap space
Red Hat Enterprise Linux 6, Red Hat Enterprise Linux 7
Amount of installed RAM
Recommended swap space
Recommended swap space if allowing for hibernation
> 2GB - 8GB
The same amount of RAM
2 times the amount of RAM
> 8GB - 64GB
At least 4GB
1.5 times the amount of RAM
^ Disk Drives: For optimum performance, run 
CA Spectrum
 on systems with Multi-disk RAID configurations @ 10,000 RPM or greater.
 
Q:  What are the OS cpu requirements?
A:
The faster the better. At the very least a very fast single core processor, again for smaller scale implementations. For medium and large implementations, 2 quad core processors (2.0+GHz) are recommended.
Q: Is it ok to run CA Spectrum on a virtual machine (vm)?
A:
Yes, however it is very important that you have DEDICATED resources for CA Spectrum (RAM and CPU). If you do not, then you will notice major performance issues. Keep in mind that CA Spectrum is enterprise software, and needs resources to be able to properly manage and monitor your network. Installing Spectrum on a vm utilizing shared resources on shared vms inhibits Spectrum's ability to perform.
Q:  Are there different capacity metrics for running the SpectroSERVER on a VM?
A:
No, a virtual machine has the same minimum/recommended specs as a physical machine. The one main difference with the vm is to make sure it has dedicated resources so that CA Spectrum can function properly.
Q: What are the required specifications for a SpectroSERVER to monitor around 20K devices and 1 million models in Spectrum 10.0?
A:
Since 1,000,000 models is at the high end of the recommendation, you will need at least 16GB of RAM (you may need 32GB depending upon how heavily utilized your SS is) and 2 quad core processors running at least 2.0GHz+.
Q: Any there any performance difference between a Linux and a Windows SpectroSERVER in 10.0?
A:
Yes, but it is a very minimal difference of less than 2%.
Q: Are there any change in resource/memory utilization in 64 bit environment?
A:
Yes, CA Spectrum will utilize more memory than previous releases due to the changes in data structure and pointers. Also, more memory will be needed if you want to have more models per SpectroSERVER than you did previously in 9.3/9.4. Due to this the minimum memory requirement is 8GB with CA Spectrum 10.0
Q: Are there any changes in the Discovery Console?
A:
 There were no changes to the Discovery Console however major discovery performance improvements were made in 10.0 to speed up the process of discovery and modeling.
Q: Any improvements for the SDM/SDC support?
A:
There were no specific improvements however we have found that in 10.0 CA Spectrum it is performing better compared to earlier releases.
Q: Is there any difference in Archive Manager in order to support the large events from more devices in x64?
A: 
 There were no specific improvements however we have found that in 10.0 CA Spectrum it is performing better compared to earlier releases.
Q: Are there any improvements for Trap Director?
A:
No specific improvements, however in our testing we have found that it performs as good as and in some cases better than 9.3/9.4.
Q: What are the limitations for creating global collections in Spectrum and in SRM?
A:
 There is no technical limit however in our testing we did experience optimal performance when using 200 global collections with 30,000 models each.
Q: How many models can I put on each SS?
A:
The recommended maximum amount of models to put on one SpectroSERVER is 1,000,000 models.  You can technically model more than that (up to 1,048,576) however you will experience performance issues. 
Q: How can I tell how many total models I have across all of my SpectroSERVERs?
A:
  You can see how many models were loaded the last time the SpectroSERVER was started by viewing the total_db_models attribute (0x12925) on the VNM model.  Review it on each SS, then add the values from all SS to see how many models you have.
Q:  How many SpectroSERVERs will I need if I am running 10.0?  Is a sizing tool available to the public?
A:
  There is no external sizing tool but there is an internal sizing utility available to CA employees to give you a recommendation on the number of SS you will need according to your configuration.  The sizer takes into account things such as the number of OneClick servers, the number of specific device types, the number of global collections etc.  In general, on average, if you figure average usage (ie one or two webservers, GCs with low model counts etc.), you can estimate around 800,000 models per SS.
Q:  How will I know when I am getting close to having 1,000,000 models?
A: 
 CA Spectrum 10.0 monitors the number of models that are modeled and will create a minor alarm at 760,000, a major alarm at 950,000, and a critical alarm at 1,040,000.  If you hit the maximum value of 1,048,576 you will not be able to create any more models.
Q: What are the limitations/recommendations?
A:
 This varies on many factors, however on average, for a
top performing
SpectroSERVER, CA recommends using 32GB of dedicated RAM with 800,000 (or less) models on each SS (assuming an SS only install).
Q: Any improvements on Spectrum Report Manager (SRM)?
A:
Yes. It has been enhanced to connect multiple SRMs to a single CABI install and there have been performance improvements to the mysql queries.  Also, the "events" table in the MySQL reporting database was partitioned for faster event report generation.  
Q:  How long will the installation of 10.0 take due to the MySQL database partitioning?
A:
 We observed that the install would take 3 to 5 minutes per 1 GB of data for the database partitioning to complete during install.  To check the size of your event reporting table, review the "event" table in the <SPECROOT>/mysql/data/reporting folder.
If you have a large SRM reporting database, this will increase the amount of time needed to install 10.0 on your OC/SRM machine.
Q:  Have any improvements been made to SSdbsave for online backup and SSdbload for restoring the database?
A:
 Yes, code changes were implemented that drastically speed up the time needed to save and load the SpectroSERVER database.
Q: How long does it approximately take to start a SpectroSERVER with 15.000 devices until all devices are activated?
A:
  This is dependent upon many factors (such as network utilization, types of devices, number of global collections, OS cpu/memory etc.) therefore every SS startup activation time is different.  More threads and tuning have been done for 10.0 though, so we expect efficient startup times.  Keep in mind that the more devices you add, the longer the activation time will take.
Q:  Is there any way to speed up model activation times?
A:
Yes, Service Performance Manager models can take a while to activate, and in 10.0 you may have many of them on one SpectroSERVER.  To speed up the SpectroSERVER model activation, you can change the following entry in the <SPECROOT>/SS/.vnmrc from no to yes:  spm_wait_activate=
This will allow the SS to activate all other models first, and change to 100% active.  Once the SS is 100% active, it will then activate the SPM models.
Q:  I heard there were more threads allocated to the SpectroSERVER, is that true?
A:
 Yes!  CA Spectrum x64 code was enhanced to allow a large increase in the total work threads (along with other SS threads) which enables you to model more, and enables the SS to process large amounts of data quickly and efficiently.  The threads have been configured from rigorous testing to perform at optimal levels out of the box.  
Q: Can real time updates be used on attributes that change often in 10.0?
A:  
Even with all of the performance enhancements in CA Spectrum 10.0 you still need to be mindful of using real time updates on global collections.  Real time updates work well on attributes that do not change often. The same caveats with real time updates still apply in CA Spectrum 10.0.
Q:  What would be a suggested limit on the number of global collections per OC server to keep the SpectroSERVER running at optimal performance?
A:
 CA recommends that creating 200 global collections with 30,000 models each is ideal for optimal performance on a SpectroSERVER that has 32GB and 800,000 models.
Q.   How many OneClick servers are recommended?
A:  
4 SpectroSERVERs per OneClick server is recommended, assuming each SS having 800,000 models and 32GB of RAM.
Q.  How many traps can each SS handle efficiently?
A:  600 traps/second sustained and 1000 traps/second peak for a window of about 10 minutes.  The SpectroSERVER will queue up traps if larger trap rates are experienced, however this leads to an increase in memory utilization during that time.
Merging Databases
Q: How can I merge databases?
A:
  The modeling gateway is needed to merge databases. There is no process during the 10.0 install to merge databases. For information on how to use the Modeling Gateway, refer to the online documentation at the following links:
Q:  What is the recommended way of merging databases?
A:
 The recommended way of merging databases is to set up a duplicate environment on new hardware.
On the new hardware, install 10.0, using the databases from the SpectroSERVERs that you want to keep, making sure to following the migration process documented in the install section.
Run modeling gateway exports on the other SS that you did not migrate
Run modeling gateway import on the 10.0 servers you are going to keep.
If you are unable to set up a duplicate environment, then migrate ALL systems to 10.0, using the standard upgrade process as documented in the Install section.
Once complete, determine which servers you want to combine.  
Run the modeling gateway export on the SS you want to get rid of.
Run the modeling gateway import on the 10.0 SS you are going to keep.
 
Q.  Can you provide an example of how you recommend merging databases?
A.
  Of course! Here is an example:
You have a total of 800,000 models spread across 5 SpectroSERVERs and you are running 9.2.3 Hotfix 12. Since you have a total of 800,000 models, you need to determine if you want one or two SpectroSERVERs. This will depend on your future capacity needs. If you have no future modeling to do, then one SpectroSERVER will be sufficient. If you expect future modeling, then 3 (three) SpectroSERVERs will be needed.  One for the Main Location Server (MLS) and 2 (two) more for the modeling (CA Spectrum best practice is to have no (zero) device models on the MLS as the MLS is used for distributed SpectroSERVER functionality).
Also, you need to determine if you are using new hardware (or new vms).  
If you are not using new hardware
 
You need to decide which SS is going to be the SS that will be running CA Spectrum. Since you are running 9.2.3 Hotfix 12, you will need install 9.4 and then 10.0 on the MLS, then the primary OC. Once those have completed and are running 10.0, install 9.4 and then 10.0 on the rest of the primary SpectroSERVERS, Once completed, then install 9.4 and 10.0 on any secondary SS and any other OneClick installs. Stop and restart the tomcat service on the primary OneClick server to update the tomcat cache..
Now that all machines are running 10.0, run the modeling gateway export on the other servers that are going to be decommissioned.
Once ready, run the modeling gateway import on the SS that will be running CA Spectrum.
Once complete, shut down the SpectroSERVER and processd on all of the decomissioned SpectroSERVERs. It is recommended that you either uninstall CA Spectrum, or at least disable processd on those boxes so they do not accidentally get started (on Windows, change the Spectrum processd service to disabled, on linux, move the processd startup scripts out of the /etc/init.d folder)
On the production 10.0 SpectroSERVERs, run mapupdate to remove the entries out of the Location server map (navigate to the SS-Tools directory in a shell and run "mapupdate -remove <landscape handle> -precedence <the_precedence value>")
If you are using new hardware (this is recommended):
(
Note:
If you are using 3 machines or more, make sure you do not model devices on your MLS. Run the modeling gateway imports on the remote SpectroSERVERs, not the MLS  Modeling gateway export of 9.2.x will work with modeling gateway import of 10.0, so if you are using new hardware, you do not need to upgrade all of the 9.2.3 H12 servers first. You can just run the modeling gateway export on the current 9.2.3 H12 and once 10.0 is installed, run the import).
From our example, you will be going from 5 to 3 SpectroSERVERs. If desired, save your SSdb and DDMdb from two of the SS and move them to the new machines (not the MLS!!) and follow the migration steps for migrating your databases (i.e. Install 9.4 on top of your database files, then install 10.0).
Since you will be decommissioning the other 3 SpectroSERVERs that are running 9.2.3 H12, run the modeling gateway export on the other 3 SpectroSERVERs. Then take the export file and import it on whichever NON MLS SS you desire.
Once all the modeling is complete, shut down the SpectroSERVER and processd on all of the decomissioned SpectroSERVERs. It is recommended that you either uninstall CA Spectrum, or at least disable processd on those boxes so they do not accidentally get started (on Windows, change the Spectrum processd service to disabled, on linux, move the processd startup scripts out of the /etc/init.d folder)
On the production 10.0 SpectroSERVERs, run mapupdate to remove the entries out of the Location server map (navigate to the SS-Tools directory in a shell and run "mapupdate -remove <landscape handle> -precedence <the_precedence value>")
Q: Is there an upgrade path from multiple SpectroSERVERs to a single SpectroSERVER?
A:
No, there is no upgrade path and the install does not do this for you. The supported method for going from multiple servers to a handful of servers would be to use the modeling gateway export/import functionality.
Q: Can I move models from one SpectroSERVER to another in a distributed environment (DSS)?
A:
  No, you cannot move models from one SS to another SS in the OneClick client using cut/paste. You would need to destroy and remodel the model on the other landscape or use the modeling gateway export/import functionality.
Q: Do we need to change the landscape value/handle after upgrade to 64 bit?
A:
No, you do not need to change the landscape handle (and you cannot without modeling gateway if you are upgrading or migrating your database). The installer will utilize the landscape handle that is already set in your database. If it is a fresh 10.0 install with no database, then you can select a landscape handle.
Q: Can I upgrade with a consolidation without recreating users, configuration management settings, and global collections, etc.?
A:
 If you install 10.0 on top of your existing install, you will retain ALL information. However if you export from your SS and import to another SS using modeling gateway, there are features that will be migrated and features that will be lost. The features that are migrated are documented in the Modeling Gateway Export functionality docs. 
Q: If I upgrade using Modeling Gateway, will I loose Event History, NCM Config History, and some other parameters?
A:
Yes, when using modeling gateway, there are some features in CA Spectrum it does not keep, such as events and NCM config history. The features that are saved are documented in the Modeling Gateway Export functionality docs.
Q: Is there any Global Modeling Catalog available? Currently in a DSS environment if a different SpectroSERVER had a different type of devices then we cannot load Device Certifications from OneClick.
A:
No, there is no global modeling catalog available. As an administrator you need to make sure that you designate one catalog as the master catalog. If you make changes to that catalog using MTE, you MUST load that catalog to all of the other SpectroSERVERs. 
Q: Can we have two models in two different landscapes connected?
A:
 While you cannot have two models in two different landscapes connected, CA Spectrum does use a proxy model  paradigm which allows you to create a "duplicate" model of the connected model in the other SpectroSERVER and connect them.
Q: Are Developer IDs preserved after upgrade or are additional steps required?
A:
 The custom/self certification is overridden after upgrade. You need to update your DB after installation.
3rd Party
Q: What version of the Java JRE is supported?
A:
 The minimum version is Java 1.8.0_31. All minor 1.8 versions will be supported.
Q:  What version of mysql ships with CA Spectrum 10.0?
A:
mysql 5.5.41
Q:  What version of Tomcat is supported?
A:
tomcat 7.0.59
Q: What version of openSSL is supported?
A:
openSSL 0.9.8zd
Q: What version of CAPKI does CA Spectrum 10.0 use?
A:
CAPKI 4.3.7
Q: What version of CABI is supported for SRM?
A:
CABI 4.1 SP3 (Patch 9 is also required to utilize multi SRM functionality).
Device Certification
Q:  What device updates were done for CA Spectrum 10.0?
A:  
Cisco IOS 15.x updates to supported MIBs 
Update MPLS-MIB for MPLS Transport Manager (Juniper)
Certify Enterasys Devices
Chassis Certification for Huawei EI
Q:  What devices were certified to work with enhanced support in CA Spectrum 10.0?
A:
  Review TEC1292545 to see what devices are updated with enhanced support in 10.0
Q.  How can I update my models to take advantage of the certification updates?
A.  You need to use the NewMM.pl script and/or destroy and recreate the models. Review TEC614051 for further details. The techdoc was written for 9.4.0 but still applies to 10.0.
Q.  If I have customized a device certification for a device that CA later certifies, will the CA device certification take precedence?
A.  No, you must remove the customized device certification for Spectrum to use the CA authored certification. If you do not want to use the CA authored device certification, then do nothing. If you do want to use it, then depending on your customization, you may need to reconfigure your models, or destroy and recreate them.
Q.  How can I configure my devices to utilize the LACP feature when upgrading to 10.0?
A.  On each upgraded SpectroSERVER there is a script named RecreateLACPModels.pl in the <SPECROOT>/Install-Tools/PostInstall directory that you need to run.  This script does not exist on fresh installs, so if you migrated your SSdb and need a copy of this script, contact CA Spectrum Support.  This script only needs to be run on migrated or upgraded databases.  It does NOT need to be run on legacy databases.  Also, after 9.4 has been installed, any newly created models that support LACP will have the functionality enabled automatically.  This functions the same in 10.0.  If you were running 9.4.x and you ran the script, you do not need to run the script again in 10.0.  You only need to run the script in 10.0 if you were running 9.2.x or 9.3.x. For more information on how to run the RecreateLACPModels.pl script, see Reconfigure LACP-Enabled Interface Models.
Q.  How can I configure previously existing NCM devices to utilize AES256 encryption?
A.  Models that were created in a prior version of Spectrum will continue to use AES128 encryption.  Models that are newly created after installing 9.4 and above will automatically utilize AES256 encryption.  To update models that previously existed, you need to reset the credentials on each device in Spectrum.  This MUST be done on a model by model basis (or you can destroy and recreate the models).  .
Q.  Do Cisco devices that are running IOS-XE firmware versions work with NCM?
A.  Yes, in CA Spectrum 9.4 as part of the certification update, Cisco devices running IOS-XE firmware will be placed in their respective device families.  The 10.0 code stream includes the same functionality.  You may need to reconfigure your devices.
GIS View
Information on the GIS view can be found in our GIS View online documentation and also in TEC1086811
Q: What values are supported in the location attribute for the GIS view? I.e. State? Country? Zip code?
A:
The GIS View utilizes Google Geocoding. Google Geocoding will interpret the information contained within CA Spectrum's device Location attribute (0x23000d) which reads the devices syslocation. For more information on what values the Google Geocoding accepts, refer to the following link: https://developers.google.com/maps/documentation/geocoding/#Types  Most standard addresses, cities, zip codes, etc. are supported values.
Q: Can I see the zip code area in the GIS view?
A:
No. Currently the GIS view does not support the zip code view.
Q: In the GIS configuration, is there any attribute available to determine the location?
A:
  Yes. Google Geocoding will interpret the information contained within CA Spectrum's device Location attribute (0x23000d) which reads the devices syslocation.
Q: Can I view different locations using one GIS map?
A:
Yes. You can view different geographical locations like North America, Africa, Australia, etc.  
Q: What are the limitations of the GIS Map? Number of devices or number of sites?
A:
There is a limit of 1000 device models in the GIS view. If more than 1000 devices are configured, only 1000 will be shown. You can utilize a Google license key to view more models.
Integration
Q: Is CA Spectrum 10.0 supported with UIM 8.2?
A:
 CA Spectrum 10.0 is supported with any version of CA UIM 8.x provided that Nisapi 8.0.1 or 8.0.4 probe is deployed with it.
Q: What version of the Nisapi probe is supported with CA Spectrum 10.0?
A:
   nisapi 8.0.4
Q:  How can I tell what version of Nisapi I'm using?
A:
 On the UIM server, check the nisapi log file: i.e: C:\Program Files (x86)\Nimsoft\probes\service\service_host\catalinaBase\logs\nisapi\nisapi.log
Q: Does the CA Spectrum to CA UIM integration support SSL in 10.0?
A:
No, the current integration does NOT support SSL. You have to disable SSL on UIM for the integration to work. SSL functionality is being considered for a future release of CA Spectrum.
Q: Does CA Spectrum 10.0 support multiple UIM instance integrations for HA (failover)?
A:
Currently no.
Q.  Where will the CA UIM models be created in CA Spectrum?
A.
 They will be created on the SpectroSERVER that was selected on the UIM Manager configuration page.
Q.  Does the CA Spectrum SOI Connector work with the CA UIM models?
A.
  Currently the CA Spectrum SOI connector will not be able to classify CA UIM VMWare entities appropriately. This is being considered for a future release of CA Spectrum
Q.  Can the UIM datacenter models be created on another SpectroSERVER?
A.
  The models can be moved after the initial implementation has been completed. Refer to technical document TEC1251313
Q.  What happens when I enable the CA Spectrum and CA UIM integration?
A.
  As soon as you click on the save button, the discovery process is initiated. Nimsoft models are created in CA Spectrum’s Lost and Found container, and as the discovery proceeds, CA Spectrum will move the models into the topology (into the Nimsoft Manager folder in the Explorer view). Be patient this first time around as this process can be time consuming. You can enable debug to watch/monitor the status of the integration. Refer below to the question and answer in regards to enabling Nimsoft debug.
Q. Can I disable the CA UIM/CA Spectrum integration to get VHM functionality back?
A.
  No, you cannot disable the integration to get VHM functionality back. You can disable the integration, but you will not be able to get the VHM functionality back unless you reinstall Spectrum.
Q.  How can I debug the CA Spectrum and CA UIM integration?
A.
  Navigate to the CA OneClick Administration page. Click on the Administration link. Click on the Debugging link. Click on the Web Server Debug (Runtime) link. Scroll down to the UIM Integration Information option and select the “On” radial button. Scroll to the bottom of the screen and press Apply. This will write debug information to the CA Spectrum OneClick tomcat log file in the <SPECROOT>/tomcat/logs directory on the CA Spectrum OneClick server.
Q: Does Spectrum 10.0 support integration with SOI 3.3 CU1?
A:
Yes, it supports SOI 3.3 CU1. Note that the connector must be configured for 64 bit (the 3.3 CU1 connector is configured as 64 bit out of the box).
Q: Any new development for integration with CA UIM?
A:
No. We intend to have some enhancements for CA UIM integration in the subsequent releases to make it cleaner.
Q: Are there any changes in the CAPC - CA Spectrum integration?
A:
Not at this time.
Q: Can Spectrum 10.0 monitor Virtual Machines, ESX hosts without depending on VAIM?
A:
CA Spectrum can monitor virtual machines using VAIM or UIM/Nimsoft (enabling the UIM virtual management disables VHM so you cannot do both).
Q.  Where can I download EEM 12.5?
A.  On the Spectrum Product Home page, under Popular Links on the right hand side, it is available in the
Additional Downloadable Resources and Tools
 
Q: What are the versions of integrated CA products that CA Spectrum 10.0 supports? 
Integration Product 
CA Spectrum 9.3
CA Spectrum 9.4
CA Spectrum 9.4.1
CA Spectrum 9.4.2
CA Spectrum 10.0
CA Application Performance Management
9.1.x
9.1.x and 9.5.x
9.1.x and 9.5.x
9.1.x and 9.5.x
9.5.x, 9.7
CA BI
3.3
3.3 and 3.3 SP1
3.3 and 3.3 SP1
3.3 and 3.3 SP1
4.1 SP3
CA eHealth
6.3.x
6.3.x
6.3.x
6.3.x
6.3.0.08 , 6.3.2.07
CA eHealth - CAC
Not Supported
Not Supported
Not Supported
6.3.2.07
6.3.2.07
CA Embedded Entitlements Manager
12.5
12.5
12.5
12.5
12.5
(no multi-domain support), 8.4
(with multi-domain support), 8.4
(with multi-domain support), 8.4
(with multi-domain support), 8.4
(with multi-domain support), 8.4
LDAP
2003, 2008
2003, 2008
2003, 2008
2008, 2012
2008, 2012
Microsoft SCOM
SCOM 2012
SCOM 2012 
SCOM 2012 
SCOM 2012 
SCOM 2012 
CA NetQOS Performance Center
6.1.x
6.1.x
6.1.x
6.1.x
6.1.x
CA NSM
11.2 SP2 Cum1
11.2SP2 Cum1
11.2SP2 Cum1
11.2SP2 Cum1
11.2SP2 Cum1
CA Performance Center
2.3.x
2.3.x
2.3.x
2.3.x
2.3.x, 2.4
REX Connector
9.3.16-R
9.3.16-R
9.3.16-R
9.3.16-R
11.0.47.1
CA Service Desk Manager/CMDB
12.6, 12.7
12.6, 12.7
12.6, 12.7
12.6, 12.7
12.6, 12.7
CA Service Operations Insight (SOI)
3.1
SOI 3.1 , 3.1 SP1, 3.2
SOI 3.1 , 3.1 SP1, 3.2
SOI 3.1 , 3.1 SP1, 3.2
3.2, 3.3
CA Spectrum SOI Connector
4
4.0 (old version scheme), 2.0.0.184
4.0 (old version scheme), 2.0.0.195
4.0 (old version scheme), 2.0.0.195
2.0.0.208
CA SiteMinder
12.5
12.5
12.5
12.5
12.5
CA UIM (Nimsoft)
NA
7.6
7.6 and 8.0
7.6 and 8.0
8.0, 8.1
CA UIM Nisapi Probe
NA
NA
8.01
8.01
8.04
Miscellaneous
Q: Has the mobile app been updated?
A:
The mobile app has not been updated and continues to function in 10.0 as it has in previous Spectrum releases.
Q: Is there a non java based web client with CA Spectrum 10.0?
A:
No, but we are developing one that we hope to provide in a future release of CA Spectrum.
Q: In Maintenance Mode, can I place different child models into maintenance mode (instead of the entire device)?
A:
   Yes, you can already put a device's interfaces and application models in maintenance mode without putting the entire device into maintenance mode. In 10.0 we added the capability to do that with ESX-VM models. For more information, see.Place ESX Host in Maintenance Mode or Hibernation v10.0.
Q: Are there any improvements for Maintenance Scheduler regarding an End Date & Time, instead of the current hours in Maintenance feature?
A:
Not at this time but this is being considered for a future release of CA Spectrum.
Q: Does 10.0 support DMVPN?
A:
Not at this time. The current integration does NOT support DMVPN. DMVPN functionality is being considered for a future release of CA Spectrum.
Q: Any updates for Service Manager/Service Dashboard?
A:
Not at this time.
Q: Do we have the possibility to restart the SystemEDGE agent from the console in 10.0?
A:
Not at this time.
Q: Any improvements for IPRM? Will it include L-VPN and MultiCast path visualizations?
A:
Not at this time.
Q: Does 10.0 Support Clustered Servers?
A:
Spectrum supports Fault Tolerance. You can install Spectrum on Clustered Servers but Spectrum wouldn’t leverage the HA aspects. You can monitor clusters through VAIM and support HACMP and MSCS.
Q: Are there any changes for the REST API?
A:
The rest api functions as it has previously but it has been enhanced to support filtering of secondary alarms. An example is provided in web services examples files (<
$SPECROOT
>/RestfulExamples/xml/FilterSecondaryAlarmsWhenInMaintenance.xml).
Q:  Are there any updates to interface performance monitoring?
A:
 Yes! in CA Spectrum 10.0 we added functionality to monitor %Port_InError, %Port_OuError, %DiscardIn and %DiscardOut. To set the thresholds, navigate to the specific interface's Threshold and Watches view, expand the Thresholds, and you can set values to monitor the %Port_InError, %Port_OuError, %DiscardIn and %DiscardOut. 
Q:  Does CA Spectrum show connectivity to WA_Links in Global Collections?
A:  
Yes! In CA Spectrum 10.0 we added functionality out of the box to show connectivity in Global Collections for WA_Links. This is configurable in the OneClick Administration -> Web Server Performance window. It is enabled by default but can cause performance issues with OneClick clients if there are many WA_Links and/or many connections.
Q:  If I was a 10.0 beta participant, can I use my database?
A:
 No, you cannot. There have been many code changes since the beta version of 10.0 was released. Using the database from your beta version on your production version will cause problems.
Q.  How come I do not have the Top Impacting Outages option?
A.
  Verify that you are running CA Spectrum 9.4.1 as an Administrator user, that your user has the Top Impacting Outages privilege enabled, and that you have SRM installed. Also, only Administrator users can access the Top Impacting Outages page. Operator users do not have access and will not see a link to the Top Impacting Outages page. For more information, see The Top Impacting Outages View section.
Q.  How come an outage does not show up in the results of the Top Impacting Outages?
A.  The outage view is limited to outages that have started AND ended within the past 30 days. If the outage started 32 days ago, it will not show up in the results. Likewise, if the outage started 3 days ago and has not ended, it will not show up in the results. 
Documentation/Learning
Q: Where is the 10.0 CA Spectrum documentation located?
A:
CA Spectrum 10.0 documentation is available at :https://docops.ca.com/display/CASP10 
Q: What is the link for the IM community?
Q: Any there any videos available for advanced concepts like South-bound gateway, Condition Correlation Editor, REST API, etc?
A:
 Vidoes are available on the CA Educate YouTube channel.