CWKS2CMDB Integration Guide

Transcription

1 CWKS2CMDB Integration Guide Version 1.4.0

2 Contents 1. Introduction Purpose Assumptions Components Overview CWKS2CMDB EIE Transfer Data from RME Database to Atrium CMDB Reconciliation Purge Installing CWKS2CMDB Installation Prerequisites EIE User RME User Installation Configuration Worksheet Installation Instructions Install Sample Reconciliation Job... Error! Bookmark not defined. 3.4 Uninstalling CWKS2CMDB Defining data transfers Data transfer overview...11 Specifying CWCLI configuration parameters Troubleshooting CWKS2CMDB Understanding performance considerations Troubleshooting server connectivity Using log messages and debug files Appendices Appendix A: Cisco RME Atrium CMDB Mapping...14 Appendix B: Cisco RME Inventory Schema Endnotes...26 CWKS2CMDB Integration Guide Page 2

3 1. Introduction 1.1 Purpose CiscoWorks Resource Manager Essentials (RME) is a network management solution for Cisco switches, access servers, and routers. The BMC Atrium CMDB (Atrium CMDB) version 2.x provides all the necessary features to implement the configuration management database (CMDB) in a customer s environment. CWKS2CMDB can exchange data between RME and the BMC Remedy Action Request System (AR System) forms or Atrium CMDB classes. This functional specification will list all the components to be developed in CWKS2CMDB, their network locations, their features, their high-level implementation approaches, and their relationships with other components. 1.2 Assumptions This installation guide assumes the following to be true prior to beginning the installation. AR System version 7.0 or greater is installed and accessible. Atrium CMDB version 2.x or greater is installed and accessible. BMC Enterprise Integration Engine (EIE) 7.0 or greater is installed and accessible. CiscoWorks RME 4.0 or greater is installed, configured and accessible. BMC Remedy Asset Management (Asset Management) version 7.0 or greater is installed and accessible (optional). It should be noted that prior customizations made to the Atrium CMDB or Remedy Asset Management system might affect the installation and operation of this integration system. 1.3 Components The following is a list of components needed for the installation of this integration system. It should be noted that all software listed must be properly licensed. RME Adapter executables. Atrium CMDB extensions. RME Adapter data package CWKS2CMDB Integration Guide Page 3

4 2. Overview Figure 1 shows how the Data Exchange application, the EIE service, and the RME CLI Framework interact with CWKS2CMDB. 2.1 CWKS2CMDB CWKS2CMDB has three primary components: the Service, the RME Adapter and the Data Exchange Application (DEA). The EIE service controls the activity between the AR System server and CiscoWorks RME. The service reads the instructions from the DEA and executes them through the RME Adapter. This is how AR Servers installed on other databases can communicate with the RME database that stores the RME s management data. The RME Adapter is used to communicate to the RME database on behalf of the service. The Service will make requests of the adapter; the adapter carries out these requests and passes the results back to the service. The Service then updates the Atrium CMDB forms appropriately. The Data Exchange Application can be installed on any supported AR System. It is the EIE Application with forms and workflow that are used to configure the integration between CiscoWorks RME and AR System server. The Field Mappings, Relationship Mappings, schedule and description of qualifying data is included in this configuration. CWKS2CMDB Integration Guide Page 4

5 2.2 EIE Transfer Data from RME Database to Atrium CMDB CWKS2CMDB is used by the Enterprise Integration Engine to query the RME database and copy all new or modified data in to the Atrium CMDB as part of the CISCO.IMPORT.RME dataset. On each run of the data exchange, records are created in the Atrium CMDB for all records found in the RME inventory which are included in this integration. If the record exists in the CISCO.IMPORT.RME dataset, the data set record is updated. If the record exists in the CISCO.IMPORT.RME dataset and no longer exists in the RME database, the data set record s status is updated to End of Life and the MarkForDelete attribute is set to Yes. This sets the stage for an optional purge operation later. Once all the data has been transferred, exchanges are defined to map all the relationships between the data that was just imported. A complete list of all relationships mapped is located in Appendix B. 2.3 Reconciliation The next step is to reconcile the CISCO.IMPORT.RME data set with any other data set. This step cannot be done until the data exchanges have completed. Out of the box the reconciliation is with the BMC.ASSET data set. If you have configured your system to have a different Master data set or wish to do reconciliation with another data set, you will need to modify these rules. 2.4 Purge Once reconciliation is complete or periodically there after, a purge job can be run to clear out entries in the RME dataset which are no longer active. You want to be sure that reconciliation has been done before the purge operation is done or your master data set will not be updated to reflect that systems or components are no longer in the RME database. An example of this purge operation is included with the integration but disabled. CWKS2CMDB Integration Guide Page 5

6 3. Installing CWKS2CMDB 3.1 Installation Prerequisites Before installing CWKS2CMDB, EIE has to be installed. EIE has the following components: Data Exchange application EIE Service The other end of the RME adapter relies on RME CLI Framework (a Command-Line Interface). Given the fact that users may not install EIE and RME in the same system, the RME Adapter will remotely invoke RME CLI commands. The RME Adapter installer will populate the following forms during installation. Even though you may enter the data manually, automating the process reduces the potential for errors and makes the task of installing the adapter easier. EIE:VendorConfiguration EIE:VendorFieldNames A sample data exchange and mappings are imported into the following forms: EIE:DataExchange EIE:DataExgLookup EIE:Data EIE:CMDBDataMapping EIE:CMDBRelMapping EIE:CMDBRelationshipData EIE:RelContainerHolder EIE:Trigger_DE The documentation of the RME Adapter will serve as an extension to the BMC Remedy Enterprise Integration Engine 7.0 Administrator s Guide EIE User Establish a user for EIE* on the Remedy server where Atrium CMDB is installed. The EIE user must be given the following permissions: 1 Fixed AR User write License 1 Fixed Asset Management user license Asset Admin group privileges (this gives computed CMDB privileges) RME User EIE must have read access to the RME inventory database where RME is installed. To that end an RME user ID must be established for use by EIE. Any user ID with access to the RME database may be used. To set a different user, see your RME Administrator. CWKS2CMDB Integration Guide 6

7 3.2 Installation Configuration Worksheet Please create the following IDs, gather the additional information, fill out the worksheet, and keep it handy, as it will be referenced in many of the following installation steps. All AR Server variables refer to the AR System server on which you wish to install the EIE Data Exchange Application. (Examples are in parenthesis) ARS Server (server name) ARS Server Admin (Demo) ARS Server Admin Password (blank) AR System Server Port Number (0) EIE Instance name (server name) 3.3 Installation Instructions To install CWKS2CMDB 1. Download the RME Adapter product. 2. Open the folder where you downloaded the RME Adapter product. 3. From the product directory, change to the directory called install_scripts\win Start the installation script by typing: install. A message similar to this one appears: D:\STI\Cisco\Beta\install_scripts\win32>install.bat The following AR servers with EIE were found: wang-ws test1 Please specify the name of your AR server from the list: 5. Enter the name of your AR system server. 6. Press Enter. This message appears: Please enter AR Server Port: 7. Enter the TCP/IP port for the AR System server, or leave it blank. 8. Press Enter. This message appears: CWKS2CMDB Integration Guide 7

8 Please enter AR Login: 9. Type the AR System Administrator ID. 10. Press Enter: This message appears: Please enter AR Password: 11. Type the AR System Administrator password, or leave it blank. 12. Press Enter: This message appears: Please enter AR Authentication: 13. Type the AR System authentication string, or leave it blank. 14. Press Enter: This message appears: You may specify the EIE instance name that you would like the sample exchange to run on. You may also change it later. Please enter EIE instance name: 15. Type the EIE Instance name, or leave it blank. 16. Press Enter: This message appears: Please enter the source dataset ID: 17.Type the source dataset ID, i.e., CISCO.IMPORT.RME. 18. Press Enter: This message appears: Please enter the source dataset name: 19.Type the source dataset name, i.e., Cisco RME. 20. Press Enter: This message appears: Please enter the target dataset name [BMC Asset]: 21. Type the target dataset name, or accept the default [BMC Asset]. 22. Press Enter: This message appears: Installation Summary: AR Server = wang-ws AR Port = AR Login = Demo EIE Instance = Source Dataset ID = CISCO.IMPORT.RME CWKS2CMDB Integration Guide 8

9 Source Dataset Name = Cisco RME Target Dataset Name = BMC Asset Press any key to continue Press Enter, to start the installation process. This message appears: Copying 6 files... Creating Windows registry... Extending CMDB classes... Importing EIE adapter data... Importing Sample reconciliation job... The installation is completed! 24. Note: You may ignore the following error if you have BMC Asset Management installed on your AR System. CMDBCreateMultipleAttribute results ReturnCode: ERROR Status List : 1 items Status Struct : Message type : ERROR Message number : Message: The attribute name is not unique. The attribute name is already in use. Appended: ClassID: BMC_CARD, Attribute Name: PartNumber Attribute: 1 CWKS2CMDB Integration Guide 9

10 3.4 Uninstalling CWKS2CMDB To remove CWKS2CMDB 1. Open the folder where you downloaded the RME Adapter product. 2. From the product directory, change to the directory called install_scripts\win Start the un-installation script by typing: install /u 4. Fill in the following information. You may skip the rest of the prompt. Please specify the name of your AR server from the list: Please enter AR Server Port: Please enter AR Login: Please enter AR password: Please enter AR Authentication: 5. At the end, you will be prompted with the following message: You may need to manually delete data from these forms in the AR User tool. The search criteria are "Vendor Application"="CiscoWorksAdapter". SCHEMA "EIE:Data" SCHEMA "EIE:DataExchange" SCHEMA "EIE:DataExgLookup" SCHEMA "EIE:VendorParamLookup" SCHEMA "EIE:VendorConfiguration" SCHEMA "EIE:VendorFieldNames" SCHEMA "EIE:CMDBDataMapping" SCHEMA "EIE:CMDBRelMapping" SCHEMA "EIE:CMDBRelationshipData" SCHEMA "EIE:RelContainerHolder" SCHEMA "EIE:Trigger_DE" The installation is completed! Use AR User tool to clean up the above forms. CWKS2CMDB Integration Guide 10

11 4. Defining data transfers 4.1 Data transfer overview This section briefly describes the steps for defining data transfers between an RME database and Atrium CMDB classes. With the exception of specifying RME configuration parameters, these steps are described in the BMC Remedy Enterprise Integration Engine 7.0 Administrator s Guide. A data transfer consists of a data exchange and a corresponding data mapping that defines the parameters under which the data are transferred. A many-to-many relationship exists between data exchanges and data mappings. That is, you can associate one data exchange with multiple data mappings, and one data mapping with multiple data exchanges. You can create data exchanges and data mappings in any order. For example, you can create a data exchange and then create one or more associated data mappings or vice versa. However, using the following suggested order might be helpful when you are first learning about the data transfer process. Again, see the BMC Remedy Enterprise Integration Engine 7.0 Administrator s Guide for more information. To create a data transfer 1. Create a data exchange 2. Create a data mapping 3. Associate a data mapping with a data exchange 4. Activate a data exchange 4.2 Specifying CWCLI configuration parameters To specify RME Adapter configuration parameters 1. Log in to BMC Remedy User. 2. Choose File > Open > Object List. The Object List window appears. 3. Select the EIE:Startup form. CWKS2CMDB Integration Guide 11

12 4. Click New. The EIE:StartUp window appears. 5. Click the Vendor Configuration tab. 6. Select the RME data exchange you want to use in the Data Exchanges table. 7. From the Parameter Name drop-down list, select ClassMask. When the selection is made, the Parameter Value field is set to the value that you set for the RME login name during installation. 8. Accept the default value in the Parameter Value field, or type a new value. 9. Click Add/Update. The parameter name and value appear in the Enter Vendor-Specific Configurations table. 10. Repeat step 7 through step 9 for each of the remaining parameters. If you have many maps, only the first data exchange need for the following parameter: Login user name for RME login. Password password for RME login. Export_URL in the format of Device_Filter if you want to limit the data transfer. CWKS2CMDB Integration Guide 12

13 5. Troubleshooting CWKS2CMDB 5.1 Understanding performance considerations TBD 5.2 Troubleshooting server connectivity TBD 5.3 Using log messages and debug files TBD CWKS2CMDB Integration Guide 13

14 6. Appendices 6.1 Appendix A: Cisco RME Atrium CMDB Mapping Cisco RME Class Note and are the key attributes, and have the format of Cisco.. The other attributes has the format of [Class].[Attribute], i.e., Cisco_Chassis.Model. BMC CMDB Class Note and Parent. are reserved for relationship mapping. Attributes in bold blue font are extended from BMC generic class, i.e., Cisco_Backplane extends BMC_BaseElement, defines Backplane Type. Source Class Attributes Attributes Target Class Cisco_Chassis BMC_Chassis Parent. Model Model HardwareVersion VersionNumber SerialNumber SerialNumber ChassisSystemType ChassisSystemType NumberOfSlots NumberOfSlots NoOfCommunication Connectors NoOfCommunicationConnector s Cisco_Backplane Parent. Cisco_Backplane extends BMC_BaseElement BackplaneType Backplane Type Model Model SerialNumber SerialNumber CWKS2CMDB Integration Guide 14

15 CWKS2CMDB Integration Guide 15 Parent. RequiresDaughterBoar d RequiresDaughterBoard Model Model SerialNumber SerialNumber LocationWithinContai ner LocationWithinContainer PartNumber PartNumber CardType CardType HardwareVersion VersionNumber Description Description OperationalStatus OperationalStatus FWManufacturer FWManufacturer Manufacturer ManufacturerName NumberOfSlots NumberOfSlots Cisco_Card NoOfCommunication Connectors NoOfCommunicationConnec tors BMC_Card Parent. ConnectorType ConnectorType Cisco_CommunicationCo nnector Description Description Cisco_CommunicationCo nnector extends BMC_BaseElement Parent. InstanceName Name FlashDeviceType FlashDeviceType Size Size NumberOfPartitions NumberOfPartitions ChipCount ChipCount Description Description Cisco_FlashDevice Removable Removable Cisco_FlashDevice extends BMC_HardwareSystemC omponent

16 CWKS2CMDB Integration Guide 16 Parent. InstanceName Name Upgrade Upgrade NeedsErasure NeedsErasure PartitionStatus PartitionStatus FileSystemSize FileSystemSize AvailableSpace AvailableSpace Cisco_FlashPartition FileCount FileCount Cisco_FlashPartition extends BMC_LogicalSystemCom ponent Parent. FileSize FileSize FileStatus FileStatus Checksum Checksum Cisco_FlashFile InstanceName Name Cisco_FlashFile extends BMC_FileSystem Parent. MemoryType MemoryType Name Cisco_PhysicalMemory Capacity Capacity BMC_Memory Parent. Description Description PrimaryOwnerName OwnerName InstanceName Name PhysicalPosition PhysicalPosition SysObjectId SysObjectId SysUpTime SysUpTime OfficialHostName OfficialHostName Cisco_NetworkElement NumberOfPorts NumberOfPorts Cisco_NetworkElement extends BMC_System

17 CWKS2CMDB Integration Guide 17 Parent. ModuleNumber ModuleNumber ModuleType ModuleType InstanceName Name EnabledStatus EnabledStatus Cisco_LogicalModule NumberOfPorts NumberOfPorts Cisco_LogicalModule extends BMC_LogicalSystemCom ponent Parent. PortNumber PortNumber PortType PortType InstanceName Name Cisco_Port If If BMC_NetworkPort Parent. InstanceName Name PoolType PoolType DynamicPoolType DynamicPoolType AlternatePoolType AlternatePoolType IsValid IsValid Allocated Allocated Free Free Cisco_MemoryPool LargestFree LargestFree Cisco_MemoryPool extends BMC_LogicalSystemCom ponent Parent. InstanceName Name OSFamily OSProductSuite Version VersionNumber Cisco_OSElement Description Description BMC_OperatingSystem

18 CWKS2CMDB Integration Guide 18 Parent. InstanceName Name ProtocolType ProtocolType Speed Speed RequestedStatus RequestedStatus OperationalStatus OperationalStatus Description Description PhysicalAddress PhysicalAddress Cisco_IfEntry NetworkAddress NetworkAddress Cisco_IfEntry extends BMC_AccessPoint Parent. Address Address SubnetMask SubnetMask Cisco_IPProtocolEndpoint DefaultGateway DefaultGateway BMC_IPEndpoint Cisco_IPProtocolEnd point IPProtocolEndpoint Cisco_PEHasIfEntry Cisco_IfEntry IfEntry Cisco_PEHasIfEntry extends BMC_Collection Parent. Antecedent Antecedent Cisco_ComputerSystemPa ckage Dependent Dependent BMC_Package Classification Classification SoftwareIdentity VersionString VersionString Cisco_SoftwareIdentity extends BMC_Collection

19 RMEPlatform Parent. Cisco_RMEPlatform extends BMC_VirtualSystem [Constant] Name 6.2 Appendix B: Cisco RME Inventory Schema <?xml version="1.0" encoding="utf-8"?> <xs:schema xmlns:xs=" elementformdefault="qualified" attributeformdefault="unqualified"> <!--This schema is based on the classes defined in Cisco Information Model V2.0 (CIMCXV2.0) Each Device has Chassis and NetworkElement. Chassis: Chassis contains a blackplane and multiple Cards. Each Card contains CommunicationConnectors and multiple daughter cards. Flash Devices reside on the Cards. NetworkElement: System Information, Interface Information and LogicalModules. LogicalModules contain OSElements and Logical Ports. The element AdditionalInformation is meant to capture device specific details that are not part of the common schema. --> <xs:element name="invdetails"> <xs:element ref="schemainfo" minoccurs="0" maxoccurs="1" /> <xs:element ref="rmeplatform" minoccurs="0" maxoccurs="unbounded" /> <xs:element name="schemainfo"> <xs:element name="rmeserver" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="createdat" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="schemaversion" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="rmeplatform"> <xs:element ref="cisco_chassis" minoccurs="0" maxoccurs="unbounded" /> <xs:element ref="cisco_networkelement" minoccurs="0" maxoccurs="unbounded" /> <xs:element ref="cisco_computersystempackage" minoccurs="0" maxoccurs="unbounded" /> <xs:element name="cisco_chassis"> <xs:element name="" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="model" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="hardwareversion" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="serialnumber" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="chassissystemtype" type="xs:string" minoccurs="0" maxoccurs="1" /> CWKS2CMDB Integration Guide 19

20 <xs:element name="numberofslots" type="xs:integer" minoccurs="0" maxoccurs="1" /> <xs:element name="noofcommunicationconnectors" type="xs:integer" minoccurs="0" maxoccurs="1" /> <xs:element ref="cisco_backplane" minoccurs="0" maxoccurs="unbounded" /> <xs:element ref="cisco_card" minoccurs="0" maxoccurs="unbounded" /> <xs:element name="cisco_backplane"> <xs:element name="backplanetype" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="model" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="serialnumber" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="cisco_card"> <xs:element name="" type="xs:integer" minoccurs="0" maxoccurs="1" /> <xs:element name="requiresdaughterboard" type="xs:boolean" minoccurs="0" maxoccurs="1" /> <xs:element name="model" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="serialnumber" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="locationwithincontainer" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="partnumber" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="cardtype" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="hardwareversion" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="description" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="operationalstatus" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="fwmanufacturer" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="manufacturer" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="numberofslots" type="xs:integer" minoccurs="0" maxoccurs="1" /> <xs:element name="noofcommunicationconnectors" type="xs:integer" minoccurs="0" maxoccurs="1" /> <xs:element ref="softwareidentity" minoccurs="0" maxoccurs="unbounded" /> <xs:element ref="cisco_communicationconnector" minoccurs="0" maxoccurs="unbounded" /> <xs:element ref="cisco_flashdevice" minoccurs="0" maxoccurs="unbounded" /> <xs:element ref="cisco_physicalmemory" minoccurs="0" maxoccurs="unbounded" /> <xs:element ref="cisco_card" minoccurs="0" maxoccurs="unbounded" /> <xs:element name="cisco_communicationconnector"> <xs:element name="" type="xs:integer" minoccurs="0" maxoccurs="1" /> <xs:element name="connectortype" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="description" type="xs:string" minoccurs="0" maxoccurs="1" /> CWKS2CMDB Integration Guide 20

21 <xs:element name="cisco_flashdevice"> <xs:element name="" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="instancename" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="flashdevicetype" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="size" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="numberofpartitions" type="xs:integer" minoccurs="0" maxoccurs="1" /> <xs:element name="chipcount" type="xs:integer" minoccurs="0" maxoccurs="1" /> <xs:element name="description" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="removable" type="xs:boolean" minoccurs="0" maxoccurs="1" /> <xs:element ref="cisco_flashpartition" minoccurs="0" maxoccurs="unbounded" /> <xs:element name="cisco_flashpartition"> <xs:element name="" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="instancename" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="upgrade" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="needserasure" type="xs:boolean" minoccurs="0" maxoccurs="1" /> <xs:element name="partitionstatus" minoccurs="0" maxoccurs="1"> <xs:simpletype> <xs:restriction base="xs:string"> <xs:enumeration value="unknown" /> <xs:enumeration value="readonly" /> <xs:enumeration value="runfromflash" /> <xs:enumeration value="readwrite" /> </xs:restriction> </xs:simpletype> <xs:element name="filesystemsize" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="availablespace" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="filecount" type="xs:integer" minoccurs="0" maxoccurs="1" /> <xs:element ref="cisco_flashfile" minoccurs="0" maxoccurs="unbounded" /> <xs:element name="cisco_flashfile"> <xs:element name="" type="xs:integer" minoccurs="0" maxoccurs="1" /> <xs:element name="filesize" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="filestatus" minoccurs="0" maxoccurs="1"> <xs:simpletype> <xs:restriction base="xs:string"> <xs:enumeration value="unknown" /> <xs:enumeration value="deleted" /> <xs:enumeration value="invalidchecksum" /> <xs:enumeration value="valid" /> </xs:restriction> </xs:simpletype> <xs:element name="checksum" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="instancename" type="xs:string" minoccurs="0" maxoccurs="1" /> CWKS2CMDB Integration Guide 21

22 <xs:element name="cisco_physicalmemory"> <xs:element name="memorytype" minoccurs="0" maxoccurs="1"> <xs:simpletype> <xs:restriction base="xs:string"> <xs:enumeration value="nvram" /> <xs:enumeration value="nvram" /> <xs:enumeration value="processorram" /> <xs:enumeration value="rom" /> <xs:enumeration value="feprom" /> <xs:enumeration value="bram" /> </xs:restriction> </xs:simpletype> <xs:element name="capacity" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="cisco_networkelement"> <xs:element name="" type="xs:integer" maxoccurs="1" /> <xs:element name="description" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="primaryownername" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="instancename" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="physicalposition" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="sysobjectid" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="sysuptime" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="officialhostname" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="numberofports" type="xs:integer" minoccurs="0" maxoccurs="1" /> <xs:element ref="cisco_logicalmodule" minoccurs="0" maxoccurs="unbounded" /> <xs:element ref="cisco_port" minoccurs="0" maxoccurs="unbounded" /> <xs:element ref="cisco_memorypool" minoccurs="0" maxoccurs="unbounded" /> <xs:element ref="cisco_ifentry" minoccurs="0" maxoccurs="unbounded" /> <xs:element ref="cisco_ipprotocolendpoint" minoccurs="0" maxoccurs="unbounded" /> <xs:element ref="cisco_pehasifentry" minoccurs="0" maxoccurs="unbounded" /> <xs:element name="cisco_logicalmodule"> <xs:element name="" type="xs:integer" minoccurs="0" maxoccurs="1" /> <xs:element name="modulenumber" type="xs:integer" minoccurs="0" maxoccurs="1" /> <xs:element name="moduletype" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="instancename" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="enabledstatus" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="numberofports" type="xs:integer" minoccurs="0" maxoccurs="1" /> <xs:element ref="cisco_port" minoccurs="0" maxoccurs="unbounded" /> <xs:element ref="cisco_logicalmodule" minoccurs="0" maxoccurs="unbounded" /> <xs:element ref="cisco_oselement" minoccurs="0" maxoccurs="unbounded" /> CWKS2CMDB Integration Guide 22

23 <xs:element name="cisco_port"> <xs:element name="portnumber" type="xs:integer" minoccurs="0" maxoccurs="1" /> <xs:element name="porttype" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="instancename" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="if" type="xs:integer" minoccurs="0" maxoccurs="unbounded" /> <xs:element name="cisco_memorypool"> <xs:element name="instancename" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="pooltype" type="xs:integer" minoccurs="0" maxoccurs="1" /> <xs:element name="dynamicpooltype" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="alternatepooltype" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="isvalid" type="xs:boolean" minoccurs="0" maxoccurs="1" /> <xs:element name="allocated" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="free" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="largestfree" type="xs:string" minoccurs="0" maxoccurs="1" /> <!--PoolType ValueMap {"0", "1", "2", "3", "4", "5", "65536"}, Values {"Unknown", "Processor", "I/O", "PCI", "Fast", "Multibus", "Dynamic"}, --> <xs:element name="cisco_oselement"> <xs:element name="instancename" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="osfamily" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="version" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="description" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="cisco_ifentry"> <xs:element name="" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="instancename" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="protocoltype" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="speed" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="requestedstatus" minoccurs="0" maxoccurs="1"> <xs:simpletype> <xs:restriction base="xs:string"> <xs:enumeration value="up" /> <xs:enumeration value="down" /> <xs:enumeration value="testing" /> </xs:restriction> </xs:simpletype> CWKS2CMDB Integration Guide 23

24 <xs:element name="operationalstatus" minoccurs="0" maxoccurs="1"> <xs:simpletype> <xs:restriction base="xs:string"> <xs:enumeration value="up" /> <xs:enumeration value="down" /> <xs:enumeration value="testing" /> <xs:enumeration value="unknown" /> <xs:enumeration value="dormant" /> </xs:restriction> </xs:simpletype> <xs:element name="description" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="physicaladdress" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="networkaddress" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="cisco_ipprotocolendpoint"> <xs:element name="address" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="subnetmask" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="defaultgateway" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="cisco_pehasifentry"> <xs:element name="cisco_ipprotocolendpoint" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="cisco_ifentry" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="cisco_computersystempackage"> <xs:element name="antecedent" type="xs:string" minoccurs="0" maxoccurs="1" /> <xs:element name="dependent" type="xs:string" minoccurs="0" maxoccurs="1" /> <!--Antecedent is the from Cisco_Chassis Element Dependent is the from Cisco_NetworkElement --> <xs:element name="softwareidentity"> <xs:element name="classification" minoccurs="0" maxoccurs="1"> <xs:simpletype> <xs:restriction base="xs:string"> <xs:enumeration value="firmware" /> <xs:enumeration value="software" /> </xs:restriction> </xs:simpletype> <xs:element name="versionstring" type="xs:string" minoccurs="0" maxoccurs="1" /> CWKS2CMDB Integration Guide 24

25 <xs:element name="additionalinformation"> <xs:element name="ad" minoccurs="0" maxoccurs="unbounded"> <xs:attribute name="name" type="xs:string" /> <xs:attribute name="value" type="xs:string" /> </xs:schema> CWKS2CMDB Integration Guide 25

26 7. Endnotes BMC and BMC Software are the exclusive properties of BMC Software, Inc., are registered with the U.S. Patent and Trademark Office, and may be registered or pending registration in other countries. All other BMC trademarks, service marks, and logos may be registered or pending registration in the U.S. or in other countries. BMC Remedy Asset Management Application, BMC Atrium CMBD, BMC Remedy Action Request System, BMC Remedy Link for SQL Server and BMC Remedy Enterprise Integration Engine are registered trademarks or trademarks of BMC Software, Inc. Cisco and CiscoWorks Resource Manager Essentials are registered trademarks or trademarks of Cisco Corporation. All other trademarks are the property of their respective owners. Copyright (c) 2007 BMC Software, Inc. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. Neither the name of the BMC Software, Inc. nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE BMC SOFTWARE, INC. OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. CWKS2CMDB Integration Guide 26