Sure. Well, to start, we're getting our computer information (server and desktop) from Tivoli inventory. We're populating the standard information, computer system, hardware system component, etc. We're also populating the IP address class from Tivoli Inventory. This is all of the IP addresses that relate to that server.
>From there, we are getting basic inventory from Cisco Works and SMARTS, which we're populating into hardware system component. We are getting information from Cisco Works on which ip addresses are hitting which network components. We use that information to create a relationship from the network hardware to the ip address, which of course is related to the computer system. We didn't use a lot of the deep classes. We kept it basic and used the CTI's to further classify the CI's. Same with the relationships. We just used the base relationships (I think we used dependant relationships for ip address to network hardware) Hope this helps. Jack -----Original Message----- From: Cindy Sapochetti [mailto:[EMAIL PROTECTED] Sent: Friday, September 22, 2006 5:18 AM To: [EMAIL PROTECTED]; Covert, Jack Subject: Re: Getting Ciscoworks data into CMDB 2.0 Hi Jack, I was wondering if you'd be able to share what classes/etc. you've been populating from Cisco/Smart? We're new to the Remedy platform and are trying to get our brains around the whole "class structure". We're currently using CMDB 2.0, and I know some of the classes have changed, but if you could see your way to sharing your current mapping, or any other info, it would sure help us out a lot. Best Regards, Cindy Sapochetti _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
