Exporting CiscoWorks RME data

Use the following process to create an import source file that contains CiscoWorks RME data, so that it is present and accessible to the server during an import task.

To generate the source file from CiscoWorks

1. Determine where CiscoWorks install directory is located on the CiscoWorks server.
2. Run the following CiscoWorks export program under installalDirory/CSCOpx/bin directory.
   • RME releases earlier than 4.0: cwexport inventory -u username -p password -f filename -continue

   • RME releases 4.0 and later: cwcli export inventory -device % -u username -p password -f filename

     username and password reference a CiscoWorks login account that has access to export
     
     filename represents the file that should then be used for the CiscoWorks DEE import

3. Move the exported filename to the server import directory (for example, D:\BCA-Networks-Data\import\filename).
   
   

   Notes

   • CiscoWorks occasionally places unreadable control characters in the export file. The file can be validated by opening a web browser that supports XML, such as Internet Explorer. Internet Explorer lists the lines in the export file that have errors. You can use a text editor to correct these errors before importing the file into the TrueSight Network Automation system.
   • The CiscoWorks data extraction engine (DEE) XML format is a very verbose format that includes a lot of inventory information. It is translated to the TrueSight Network Automation internal XML format during the import process using XSL, which is a memory-intensive process.

    

   If you get an OutOfMemory error during the import, break the input file into smaller pieces and import them individually.
   
   As an example of how to perform this task, the following is a DEE file that contains two devices (Device-A and Device-B):

   {{<?xml version="1.0" encoding='ISO-8859-1'?>}}{{<InvDetails>}}{{<SchemaInfo>}}{{<RMEServer>...</RMEServer>}}{{<CreatedAt>....</CreatedAt>}}{{</SchemaInfo>}}{{<RMEPlatform>}}{{...}}{{<InstanceName>Device-A</InstanceName>}}{{...}}{{</RMEPlatform>}}{{<RMEPlatform>}}{{...}}{{<InstanceName>Device-B</InstanceName>}}{{...}}{{</RMEPlatform>}}{{</InvDetails>}}

   
   The <RMEPlatform> tags encapsulate the data for a particular device being imported. The preceding example could be broken down into two files as follows:

   {{<?xml version="1.0" encoding='ISO-8859-1'?>}}{{<InvDetails>}}{{<SchemaInfo>}}{{<RMEServer>...</RMEServer>}}{{<CreatedAt>....</CreatedAt>}}{{</SchemaInfo>}}{{<RMEPlatform>}}{{...}}{{<InstanceName>Device-A</InstanceName>}}{{...}}{{</RMEPlatform>}}{{</InvDetails>}}{{}}{{<?xml version="1.0" encoding='ISO-8859-1'?>}}{{<InvDetails>}}{{<SchemaInfo>}}{{<RMEServer>...</RMEServer>}}{{<CreatedAt>....</CreatedAt>}}{{</SchemaInfo>}}{{<RMEPlatform>}}{{...}}{{<InstanceName>Device-B</InstanceName>}}{{...}}{{</RMEPlatform>}}{{</InvDetails>}}